Status Update
Comments
ha...@gmail.com <ha...@gmail.com> #3
Deleting one would mean that it wouldn't anymore.
sr...@gmail.com <sr...@gmail.com> #4
mi...@gmail.com <mi...@gmail.com> #5
existing issue and expecting that to work out.
je...@gmail.com <je...@gmail.com> #6
seems to be a common issue.
ma...@google.com <ma...@google.com> #7
should be noted:
1. There is now 10 apps given per developer
2. You can re-use an App id
3. Deleting an existing datastore is a separate issue.
am...@gmail.com <am...@gmail.com>
no...@gmail.com <no...@gmail.com> #8
the application then recreate it. Hope both features will available soon.
we...@gmail.com <we...@gmail.com> #9
ji...@gmail.com <ji...@gmail.com> #10
I'm trying to do some GAE development for clients, but I have almost run out of slots. When I was initially
playing around with the system, I was rather liberal with creating applications, and now with no way to delete
or rename them, I'm stuck with the application names I initially chose (and which I no longer want to use).
In the short run, it would be nice if there was an email address documented somewhere so we could ask for
the apps to be manually deleted or renamed (as is the case when more quota is needed).
ya...@gmail.com <ya...@gmail.com> #11
1. Create a new google account.
2. Add the new google account as a developer for the app you want to get rid of.
3. Remove your real account from the app.
I didn't try this yet, but it should work. Please let us know if it doesn't.
ji...@gmail.com <ji...@gmail.com> #12
I tried your proposed workaround. Unfortunately, when you give your applications
away to the other user, you don't get to create a new one.
I now have 9 apps on my dashboard, but I don't have the option to create another one.
I'm also a bit pissed off about the SMS authorization scheme they've introduced - it
may or may not cost me $5 because my cell phone company (Rogers in Canada) is evil.
It took me about an hour of messing around with their gateway and resending the SMS
to get my code. Not Google's fault really - but why build a dependency in on such a
brain-damaged third-party system?
App Engine is a pretty cool system that I'd like to promote as part of my
professional practice, but it's not clear to me that Google is positioning it as
anything other than a 'hobby' tool.
[Deleted User] <[Deleted User]> #13
ab...@gmail.com <ab...@gmail.com> #14
pc...@gmail.com <pc...@gmail.com> #15
This is one of the oldest issues.
This issue has never been addressed by anyone from google.
There is a published workaround that doesn't work.
The solution seems so ridiculously simple.
I can only assume that google can't delete applications, and that there is a limited
pool of slots for potential applications. Is this the case? *knock* *knock* google,
is anyone listening?
to...@gmail.com <to...@gmail.com> #16
al...@gmail.com <al...@gmail.com> #17
been previously controlled by someone else. It's described in the "Domain
Contamination" article by Amit Klein
(
to cause some malicious pages to be cached indefinitely.
ba...@gmail.com <ba...@gmail.com> #18
doesnt make sense to 'take' domains just because you can - in case you might want it.
pa...@gmail.com <pa...@gmail.com> #19
to enable deleting. In one case I set the wrong auth method for a domain and in
another I made a typo. The auth method is another issue but in the short term there
isn't a way around it which brings us to this issue and typo is human error however
if there was a period (maybe an hour after creation?) where it could be deleted this
would mitigate domain squatting and issues with domain contamination.
tb...@gmail.com <tb...@gmail.com> #20
mo...@gmail.com <mo...@gmail.com> #21
feet wet. If they get to the point of wanting to actually deploy apps "for real" this
could be a real issue. I know this is still Beta (it is Google after all), so maybe
this will get resolved eventually. Meanwhile, I'm starring this issue.
[Deleted User] <[Deleted User]> #22
the versions of an application and its data. If I have to pick one of the two,
deleting all the data at once is more important.
pr...@gmail.com <pr...@gmail.com> #23
[Deleted User] <[Deleted User]> #24
se...@gmail.com <se...@gmail.com> #25
issue is solved.
sa...@gmail.com <sa...@gmail.com> #26
mo...@gmail.com <mo...@gmail.com> #27
ng...@gmail.com <ng...@gmail.com> #28
ye...@gmail.com <ye...@gmail.com> #29
[Deleted User] <[Deleted User]> #30
ka...@gmail.com <ka...@gmail.com> #31
xc...@gmail.com <xc...@gmail.com> #32
pc...@gmail.com <pc...@gmail.com> #33
testing application with multiple versions; my pre-release projects share the same
application name, and I change the version number when I start work on a new project.
Seems to work fine.
mc...@googlemail.com <mc...@googlemail.com> #34
the app and more importantly, delete all the data files associated with it.
I can login to my admin area, but other than that, I have no idea about deleting or
doing anything on app engine.
Please put a delete key button on the manage app page or if you must, a dustbin
symbol.
mi...@gmail.com <mi...@gmail.com> #35
im...@gmail.com <im...@gmail.com> #36
sl...@gmail.com <sl...@gmail.com> #37
application IDs they'll need in the long term. Some people come to App Engine with a
specific application in mind. Others want to run a few experimental apps now but
maybe replace them in the future.
It's surprising that Google has never even given a reason for this policy. The
closest I've heard is a tentative "There may be a security issue if somebody else
registers the same ID and ensnares your users who still think it's the other
application." But this is nonsense because DNS does allow somebody to register an
expired domain, and that has not been a major avenue for trojan horses or outraged
users. If the user is merely *disappointed* that one application has been replaced
by another, well so what? And App Engine IDs are *less* vulnerable than domains
because they do not automatically expire when somebody doesn't pay the bill.
Perhaps it's technically difficult to delete an application and disassociate the ID
from the user. If so, pray tell us why. Users delete entities all the time; why
can't Google just delete the application's files and Datastore data? Marking the ID
as "available" while keeping a history of its ownership for billing records may be
harder, but even a "Disable this application" button on the console would alleviate
half of users' concerns while something is being done to recycle the IDs.
To #35 (mcl.office): use the Datastore viewer to determine which entities remain, and
write an application that deletes them all. Also note the application's versions in
the admin console, and upload an empty application into every version; e.g., an
app.yaml pointing to a nonexistent file, or a trivial "hello world".
bd...@msn.com <bd...@msn.com> #38
applications when it appeared as though it hadn't succeeded so now I have multiple names that are very similar
which is obviously pointless. I would like to rectify this. Thanks.
[Deleted User] <[Deleted User]> #39
ke...@gmail.com <ke...@gmail.com> #40
around with, but don't want to keep on 'my permenant record'. This seems to me to be
a must-have feature to take the app engine as a serious platform. 10 Apps and then
creating a new Google Account just for the others seems a bit limited.
ak...@gmail.com <ak...@gmail.com> #41
you have. I'm in the same bucket of created a few test apps (I even created one to
test if deleting the app is possible immediately after creating it), and now I'm down
to 7 app ids remaining.
The mapping to a URL is not that big of a deal if you have a google apps domain, you
can map the GAE app to any URL you please as you already own that domain.
ad...@gtempaccount.com <ad...@gtempaccount.com> #42
- Manage my App, but they still exist
- Verify another account with my phone number
jo...@gmail.com <jo...@gmail.com> #43
eg...@gmail.com <eg...@gmail.com> #44
But I'm a straight up Google fan boy, and I don't want to do you this way. Sigh, but
if I must .... For me, it's not about deleting the data. It's about thinking of
really cool new names for my apps, and not wanting to go off and register the
domains, etc. Hey, wait a minute. About allowing aliases for apps? Is that any
easier? I just wanna use my new cool app name. Is that so wrong?
dn...@gmail.com <dn...@gmail.com> #45
instead of feature. we should push google a lot, otherwise they probably won't
implement this.
tj...@gtempaccount.com <tj...@gtempaccount.com> #46
Agreed at least on the priority front. If you can create something, you must be able
to delete it. That's Version 0.1 functionality, full stop. It is not a "nice to
have". It is not something to implement only if enough people ask for it. It's a
"don't even bother to open the doors until you have this" item. Astonishing to have
gone to beta without it, much less to STILL not have it on the roadmap.
bt...@brandonthomson.com <bt...@brandonthomson.com> #47
the 10 limit. Most probably the deletion is not such a simple feature to implement
and google is rightly focusing their limited resources on more useful lines of
development
re...@gmail.com <re...@gmail.com> #48
A higher priority would reflect the interest people have in fixing the issue.
However, while it may or may not be difficult to implement the ability to delete an
application, I doubt Google would shrink from addressing the task unless there
weren't another compelling reason - Google does not have a history of backing down
from a complicated assignment, particularly when utility is at stake. I suspect the
low and flexible-at-their-discretion limit, coupled with the inability to remove a
name once assigned is simply a deterrent to name squatters. But who knows, they
remain tight-lipped on the matter. Maybe it is time to return to the newsgroup and
make some noise about it there - it's obviously being ignored here as a low-priority
feature request...
sc...@gmail.com <sc...@gmail.com> #49
This gets to some of the basic "user rights" of which we have now. We should have the right to create, edit and
delete out own content!
rr...@gmail.com <rr...@gmail.com> #50
ne...@gmail.com <ne...@gmail.com> #51
ja...@gmail.com <ja...@gmail.com> #52
[Deleted User] <[Deleted User]> #53
al...@gmail.com <al...@gmail.com> #54
di...@gmail.com <di...@gmail.com> #55
ko...@gmail.com <ko...@gmail.com> #56
mind that once we delete an application, we can only create another application
30-days from today.
The fact is, when I started, I created an app called myfirst-xxx, which is natural to
me, since I always start developing apps, technology test programs and even write in
a new programming language by creating a myfirst program.
Therefore, I think Google should seriously consider this 'feature'. Rename or Delete
doesn't matter, they will really help developers, especially those who just get
started using Google AppEngine
ye...@gmail.com <ye...@gmail.com> #57
issue instead of posting meaningless +1. Explanation here:
Application's name is a branding issue. If I am developing an application for
important to me, because I will have to redirect the user to
want to do SSL. Deleting an application is part of that.
le...@gmail.com <le...@gmail.com> #58
obviously important. At the least there should be a dang html change to make the
user aware of this severe unexpected limitation when they are making the application
ids in the first place so that they don't fill their 10 slots with garbage like
helloworld123423, helloworl234248998, etc..............
mo...@gmail.com <mo...@gmail.com> #59
ge...@gmail.com <ge...@gmail.com> #60
al...@gmail.com <al...@gmail.com> #61
feature. Is somebody just lazy or is there a technical difficulty?
tj...@gtempaccount.com <tj...@gtempaccount.com> #62
> Why has this been open for A YEAR?
Wow, that is surprising.
> Is somebody just lazy or is there a technical difficulty?
I very much doubt it's laziness, but I also very much doubt it's that difficult to do
technically. There's a corporate reason for not doing this, or for prioritising it
so low as to effectively not do it.
But a year on, it's really WELL past time for Google to A) Explain why they haven't
already done this, and B) Commit to an ETA for doing it despite their obvious
reticence. It can have all sorts of caveats, like: No one (not even the original
author) can reuse that app name for 30 days / 90 days / a year / whatever. But just
do it already.
@all:
PLEASE don't pile on with concerns about people jumping on an old app name and masquerading as the original app, etc., etc. If a developer releases an app name,
it's their own lookout, not Google's problem. Concerned about someone jumping on it?
Put a parking page there for a year before you release it (and live with the fact it
eats one of your quota).
--
T.J. Crowder
tj / crowder software / com
Independent Software Engineer, consulting services available
se...@gmail.com <se...@gmail.com> #63
sl...@gmail.com <sl...@gmail.com> #64
why. It's not that they aren't aware of how strongly people feel about this. People
ask the developers this all the time, and anybody who reads this issue knows there's
widespread frustration. THE BEST THING TO DO IS TO STAR THE ISSUE, because the
number of stars seems to be what gets Google's attention. Repeating the same
comments that others have made doesn't really help, what you need to do is GET ALL
YOUR COWORKERS TO STAR THE ISSUE. If I'm reading the index correctly, this is the
5th most popular issue, but it has less than half the number of stars as 4th place.
ha...@content-studios.com <ha...@content-studios.com> #65
iw...@gmail.com <iw...@gmail.com> #66
really don't get this.
[Deleted User] <[Deleted User]> #67
an...@gmail.com <an...@gmail.com> #68
misspelled(twice) my application name and created several apps that I don't need.
br...@gmail.com <br...@gmail.com> #69
has never been deployed.
If we ask for a more specific problem to be solved, perhaps someone at google can fix
it. Please go to
an...@gmail.com <an...@gmail.com> #70
ko...@gmail.com <ko...@gmail.com> #71
implement this functionality.
sf...@gmail.com <sf...@gmail.com> #72
[Deleted User] <[Deleted User]> #73
during the last week.
Please guys learn how to star rate a issue, if you can't don't be supprised you will
get ignored. JUST CLICK ON THE >>STAR ON THE TOP LEFT CORNER<< infront of the
headline "
ta...@gmail.com <ta...@gmail.com> #74
si...@gmail.com <si...@gmail.com> #75
le...@gmail.com <le...@gmail.com> #76
rc...@gmail.com <rc...@gmail.com> #77
an...@gmail.com <an...@gmail.com> #78
ka...@gmail.com <ka...@gmail.com> #79
ka...@gmail.com <ka...@gmail.com> #80
the priority of this issue
si...@gmail.com <si...@gmail.com> #81
[Deleted User] <[Deleted User]> #82
lg...@gmail.com <lg...@gmail.com> #83
on your hands.
sc...@gmail.com <sc...@gmail.com> #84
ub...@gmail.com <ub...@gmail.com> #85
(certainly not google) the only way to get things moving is to start blogging &
twiting about it and perhaps even start re-evaluating AppEngine viability all
together. But the key point - let the world know!!!
dy...@gmail.com <dy...@gmail.com> #86
comments like "I agree" or "Please do this" or "Change the Priority." It's really
spamming the inboxes of everyone following this (a whole 632 people). Those who
starred it want this feature too, but thankfully most people aren't replying with
stupid comments.
As for the priority, low priority makes sense. Perhaps this is a good feature and
something a lot of people want, but that doesn't change the fact that it's minimal
compared to the other issues they have on their hands. Be more careful with the apps
you create. Most people complaining here probably don't even have 10 apps already,
maybe don't even have 3. I'm not sure that it's really a "joke," and please, blogging
and tweeting about this, which is hugely trivial for anyone using it as a free
service, is just plain ridiculous and will only guarantee that people see you as
annoying.
Yes, I want this too. But please stop whining. We'll get it when/if we get it. I'd
love to know why we can't in the first place, but there probably *is* a reason. The
world doesn't revolve around any of us, and in the grand scheme of everything we do,
being able to delete one of our apps on AppEngine is more trivial then most of our
issues.
sc...@gmail.com <sc...@gmail.com> #87
should include the right to delete something we create. And don't think google is doing us any favors with
these free offerings, they need developers as much as we need them. So no, please don't sit down and shut
up. If you think this is an important issue say so. If people don't want to see these emails they can filter
them.
Don't get me wrong I love what google has done here and elsewhere, but they are still a corporation. If they
want my business they should work for it.
et...@gmail.com <et...@gmail.com> #88
issue seems pretty simple?
1. If you don't like the name you chose, get a domain and use
google apps to point to your application.
2. Delete any database content.
3. Change the version number in app.yaml. Delete all other
content and upload it. Then delete all other versions of your
application.
I totally agree you should fight your rights online. However
being upset that on a predominantly free service you chose the
name
big of a deal. Please focus on issues for which there are no
workaround. And if you are paying and are upset I'm pretty sure
you can afford a domain.
I really appreciate this service the way it is, free. Please don't force them to make us pay for it so they can
solve all of our issues for us.
Finally, please be aware all these comments are causing
people to unstar this issue to stop the emails, as many have
pointed out. (and yes I realize I'm being hipocritical)
mc...@googlemail.com <mc...@googlemail.com> #89
I no longer require those apps and I wish to remove all trace of them
from the internet, as the data was held in text files, not in the 'Big Store' or
whatever name they gave for their storage system.
I can manage to access the dashboard, but nothing else and I want to
DELETE those apps.
So please no stupid messages about NOT DELETING being that important -
it is a MUST.
Imagine a database without the ability to delete a record, the world
would be covered with data storage systems. I can see myself now,
drowning in a sea of 8" floppy disks !!!!!!
ub...@gmail.com <ub...@gmail.com> #90
These are *NOT* stupid comments, these are just feedback and input from a community
of users who want to use this service but "something" is holding them back. Staring
is one thing, but people should and do have their rights to also express their
opinions in words, even if.. yes.. even if it slightly irritates you! Hey... you
probably just expressed your opinions in more words then anyone else. And yes... even
their doing it with only a few words like "I agree" or "please add this", it's their
right to do so and that their way of putting some pressure on Google to add this, so
let people express their feeling in whatever way they want (as long as they don't
hurt anyone while doing so... and so far no one did!).
know I just don't see how this has anything to do with any of the points made... it
completely irrelevant! As far as the priority of this issue, well.. I guess the issue
tracker doesn't lie - fact is, this is the one issue with most votes. Fact is, people
really miss this feature, not just as a nice to have one, but as an important one.
One very valid suggestion wast to at least enable renaming an application rather than
deleting it. I myself have only 3 applications and then I found out that I cannot
delete or renamed them and that's stopped me from creating new ones... why would I? I
definitely don't want to start naming my applications app1, app2, app3 and os on just
to keep them generic to fit all my needs. I don't care what other high priority
issues they have in the queue... this should definitely be one of them as it drives
people away and prevent the community from following on this technology.
>and tweeting about this, which is hugely trivial for anyone using it as a free
>service, is just plain ridiculous and will only guarantee that people see you as
>annoying.
Welcome to the 21st century. Again... if something itches people, then they blog
about it or twit about it... You may find it ridiculous, but what can you do about
it, millions of other people in the world disagree with you. It would be funny to see
you fight it though.
but over the 80+ people who're trying to use the AppEngine for meaningful stuff. If
you have a concrete opinion about this issue, feel free to add a comment and express
your opinion about it, but please don't be arrogant and express your opinion about
the people! what makes you so special and so better then the rest of us? And "the
world doesn't revolve around any of us", of course not... the world is much more than
AppEngine, Java, Python, Computers or any of these. But I'll tell you what, community
driven products *do* revolve around the community... and the community as a whole is
us (including you my friend).
Bottom line: live and let live, concentrate and focus on actual content and not on
people, and we'll all live in peace. And you know what... if you're really, but
really, frustrated about the people, you can blog & twit about it too :-)
st...@gmail.com <st...@gmail.com> #91
[Deleted User] <[Deleted User]> #92
wk...@gmail.com <wk...@gmail.com> #93
an...@gmail.com <an...@gmail.com> #94
al...@kojevnikov.com <al...@kojevnikov.com> #95
th...@gmail.com <th...@gmail.com> #96
tj...@gtempaccount.com <tj...@gtempaccount.com> #97
[Deleted User] <[Deleted User]> #98
vs...@gmail.com <vs...@gmail.com> #99
architecture they want to keep secret.
I respect that as a developer.
[Deleted User] <[Deleted User]> #100
br...@gmail.com <br...@gmail.com> #101
[Deleted User] <[Deleted User]> #102
described here:
appengine/browse_thread/thread/d5c17a116e81d266?hl=en
I have a testing app that is misbehaving. I really do not care about the app at this
poing, I have all code and data backed up and can recreate if from scratch. If I
could I would just delete the whole thing and recreate it but because I cannot
delete an app and its data and I can only have 10, I keep pinging Google to clean it
up for me becoming one more support case.
So adding support to delete apps will probably decrease Google's support load for
mundane things allowing them to focus on major issues.
ce...@gmail.com <ce...@gmail.com> #103
bn...@gmail.com <bn...@gmail.com> #104
rd...@gmail.com <rd...@gmail.com> #106
il...@gmail.com <il...@gmail.com> #107
rs...@gmail.com <rs...@gmail.com> #108
ma...@google.com <ma...@google.com> #109
* The ability to clear the datastore. (This can be done today with code and remote_api, but not in the admin console.)
* The ability to stop an application from serving. You can do this by uploading a blank application as described in
* The ability to create additional applications, in particular to go beyond the quota of 10 (originally 3). You can
request a quota bump just for this, and you can also re-use a single application for testing over and over again.
* The ability to hide an application from the "My Applications"/"All Applications" page in the Admin Console.
* The ability for a future developer to get access to the created application name.
* The ability to rename an application. Note that you can serve from almost any domain name using
We are working on some of these now, but not all of them; it may make sense to split this issue into multiple issues and
reference them here so people can vote on them.
Also, I am going to delete all of the 'me too' comments. Please use the star.
ne...@gmail.com <ne...@gmail.com> #110
> with code and remote_api, but not in the admin console.)
Not always. It is possible in a couple of hours to add enough data to Datastore that
it takes over a week of execution to remove it all. One reason for this inequality
is that insertion of multiple rows can be done efficiently using a group, whereas
there is no way to build a bulk deletion script of anywhere near the same efficiency
if one doesn't have knowledge of which records form a group. The other reason for
the inequality is the time spent waiting for submarine data to surface and become
available for deletion.
ni...@gmail.com <ni...@gmail.com> #111
Hello Matthew, you forgot one request :
* The ability to delete an application
This is a true story, only with names expleted. I've created with a cool name, say,
"foobarz". After a while, it got to me that the name would be even cooler if it was
"foobars". So I created another app with the new proper name.
OK so now I've got "foobarz" and "foobars" in my application list. I know I can erase
the old app by putting a blank app in it. In fact I put an app that redirects
everything from "foobarz" to "foobars". But it just looks bad when I see the
application list. I just want to forget about the old name, it was so uncool !
At this point, I cannot delete the app. I don't want to re-use it for another
purpose, since the name is not cool anymore, plus it's too close from the other,
good, application name.
So all in all I've got a huge wart popping at my face each and everytime I connect to
the AppEngine console, and it says "Google doesn't know how to delete something it
created", and all my friends laugh at me, and Google.
OK, that last part about my friends was not true, but the rest is. My point is : it
just doesn't makes sense that we have to provide hundreds of justifications of why we
need the "delete" function.
It is a bit like we were discussing with a keyboard maker about the need to add a
"delete" key and the keyboard maker kept on saying "hey, you don't need that, just
select the characters you want to remove and press the space key".
It's just a standard practice to provide a "delete" button each time there's a "Add
new" button, and given enough time people will come up with other useful use cases
for this function.
So please, pretty please, add this not-so-cool but fundamental function to the
otherwise awesome GAE.
Regards,
Nicolas
el...@gmail.com <el...@gmail.com> #112
First, I'd like to note that the fact that a certain feature is achievable by other
means does not mean it is unneeded, and definitely not that this feature-request
should be removed.
For example, Gmail has added "move to label" button, even though it was perfectly
possible to label and then unlabel it before. The fact that it is a common task many
people wish to accomplish, justify a feature request for a single button that would
do all the hard work.
Second, the feature "delete an app" include one more requirements than what you
mentioned:
* Release a certain application name to the public domain, ie, enabling other users
to build application with the application-id you previously used. If I had a website
on
and use
None of the features you listed allows me to release the application-id, and allow
everyone to use it.
Obviously when this is possible, there's no need to bump up the quotas, and there's
no point with listing it in your admin console. Also renaming can be implemented
using the delete feature, so this feature covers three of your points. But those are
different features and those features nothing to do with the main
release-app-id-to-the-public feature which is being asked here.
we...@gmail.com <we...@gmail.com> #113
th...@gmail.com <th...@gmail.com> #114
getting worse everyday, I'm unsubscribing.
ca...@gmail.com <ca...@gmail.com> #115
Google: Don't leave us in the dark. That isn't fair, and it isn't right. Provide us with two things: a "delete app"
function, and an explanation why you are ignoring all these requests.
(Dylnuge,
for saying so!)
ia...@gmail.com <ia...@gmail.com> #116
wa...@gmail.com <wa...@gmail.com> #117
you will fill the 10 applications with no mind at the first time.
every 10 application will disable 10 gmail accounts,
so they won't let you delete the application when you want, you must think carefully
when you creat it.
tu...@gmail.com <tu...@gmail.com> #118
tr...@gmail.com <tr...@gmail.com> #119
quota is the first thing I looked for when signing up. I am reluctant to invest time
in migrating to this platform without having those features or at least a way around
the limit beyond setting up new Google accounts all the time.
Is it at all possible to have more than a limit of 10. There was something mentioned
about being bumped up a level when needed? Is that an official service ?
Many thanks in advance.
pe...@gmail.com <pe...@gmail.com> #120
No DRM.. Hey its cool guys dont winge.
oz...@gmail.com <oz...@gmail.com> #121
name specific to the project. I really want to delete that application.
aa...@gmail.com <aa...@gmail.com> #122
mu...@gmail.com <mu...@gmail.com> #123
accidentally just killing my quota.
de...@gmail.com <de...@gmail.com> #124
kr...@gmail.com <kr...@gmail.com> #125
js...@gtempaccount.com <js...@gtempaccount.com> #126
mi...@gmail.com <mi...@gmail.com> #127
* Many useless projects/applications;
* Used domain names;
I wat to delete a project and create a new one. For this new one, I've tried lots of
diferent names but they are all being used, or not. I try to visit each one I try but
theres only blank pages.
ra...@gmail.com <ra...@gmail.com> #128
people getting frustrated in the sign up process because someone created an app in
that name and then never actually wrote anything, i have 2 apps i wanted to start,
but never got around to, now these names are taken. so in theory, google may have
lost 2 users just from that..
ui...@gmail.com <ui...@gmail.com> #129
ma...@gmail.com <ma...@gmail.com> #130
ka...@gmail.com <ka...@gmail.com> #131
ka...@gmail.com <ka...@gmail.com> #132
f....@gmail.com <f....@gmail.com> #133
ei...@gmail.com <ei...@gmail.com> #134
I would be happy if I could rename my Apps.
no...@gmail.com <no...@gmail.com> #135
would be able to delete as well as add!
ji...@gmail.com <ji...@gmail.com> #136
ji...@gmail.com <ji...@gmail.com> #137
mp...@gmail.com <mp...@gmail.com> #138
ca...@gmail.com <ca...@gmail.com> #139
sv...@gmail.com <sv...@gmail.com> #140
hard) should be possible and especially true when you have a limited amount of quote
available. Dont count disabled ones towards quota, may be?
vi...@gmail.com <vi...@gmail.com> #141
lu...@gmail.com <lu...@gmail.com> #142
mj...@gmail.com <mj...@gmail.com> #144
go...@gtempaccount.com <go...@gtempaccount.com> #145
If your app id were freed, someone else could snatch it up. Users of your old service
might give private information to the new service, thinking it to be your service.
jo...@google.com <jo...@google.com> #146
it...@gmail.com <it...@gmail.com> #147
tu...@gmail.com <tu...@gmail.com> #148
su...@gmail.com <su...@gmail.com> #150
ch...@gmail.com <ch...@gmail.com> #151
maybe it would be ok to let people release domains if the app has never been deployed?
xi...@gmail.com <xi...@gmail.com> #152
hn...@gmail.com <hn...@gmail.com> #153
ep...@gmail.com <ep...@gmail.com> #154
fi...@gmail.com <fi...@gmail.com> #155
if not then tell me how to delete my draft so that name and space saved for others. Irritating to see that draft as no need of that app and no need to publish it.
fi...@gmail.com <fi...@gmail.com> #156
[Deleted User] <[Deleted User]> #157
th...@gmail.com <th...@gmail.com> #158
co...@gmail.com <co...@gmail.com> #159
ya...@google.com <ya...@google.com> #160
If you want to remove your resources from the Google Cloud Platform entirely you can remove each deployed version and service configuration of your application or delete your Cloud Platform project.
If one of your uses cases is not covered by these options, please create a new feature request on this issue tracker. [3]
[1]
[2]
[3]
lo...@gmail.com <lo...@gmail.com> #161
ve...@g-experts.net <ve...@g-experts.net> #162
re...@gmail.com <re...@gmail.com> #163
ve...@g-experts.net <ve...@g-experts.net> #164
re...@gmail.com <re...@gmail.com> #165
sl...@sada.com <sl...@sada.com> #166
ga...@gmail.com <ga...@gmail.com> #167
ma...@intrusted.co.uk <ma...@intrusted.co.uk> #168
ri...@gmail.com <ri...@gmail.com> #169
[Deleted User] <[Deleted User]> #170
se...@porsche.digital <se...@porsche.digital> #171
da...@gmail.com <da...@gmail.com> #172
ro...@gmail.com <ro...@gmail.com> #173
I created an app in an existing project to do a tutorial and picked the wrong region. I could not delete the app and therefore could not change the default app region. So I had to migrate my ENTIRE existing project to the new region so I could take advantage of private network. It is such a BASIC feature and it concerns me that it does not appear like google takes its feedback from their customers seriously..
n....@gmail.com <n....@gmail.com> #174
sz...@innonic.com <sz...@innonic.com> #175
an...@gmail.com <an...@gmail.com> #176
sp...@gmail.com <sp...@gmail.com> #177
Why should anyone use a platform as broken as this one?
[Deleted User] <[Deleted User]> #178
ve...@g-experts.net <ve...@g-experts.net> #179
Thus disabling an application is not enough, deleting an application would perhaps allow this, however.
[1]
ki...@gmail.com <ki...@gmail.com> #180
ma...@gmail.com <ma...@gmail.com> #181
ji...@gmail.com <ji...@gmail.com> #182
ja...@gmail.com <ja...@gmail.com> #183
jo...@gmail.com <jo...@gmail.com> #184
mg...@gmail.com <mg...@gmail.com> #185
ma...@gmail.com <ma...@gmail.com> #186
way the system works :(
Regards,
Max Lynam
On Sat, Dec 28, 2019 at 9:33 AM <buganizer-system@google.com> wrote:
ma...@gmail.com <ma...@gmail.com> #187
I SECOND THAT. IT IS PLAIN RUBBISH
rv...@cisco.com <rv...@cisco.com> #188
sp...@gmail.com <sp...@gmail.com> #189
As a software architect there is no way I would recommend Google platform for anything serious.
jp...@gmail.com <jp...@gmail.com> #190
sj...@gmail.com <sj...@gmail.com> #191
pa...@gmail.com <pa...@gmail.com> #192
od...@gmail.com <od...@gmail.com> #193
[Deleted User] <[Deleted User]> #194
co...@gmail.com <co...@gmail.com> #195
[Deleted User] <[Deleted User]> #196
[Deleted User] <[Deleted User]> #197
a....@gmail.com <a....@gmail.com> #198
[Deleted User] <[Deleted User]> #199
[Deleted User] <[Deleted User]> #200
ld...@gmail.com <ld...@gmail.com> #201
ju...@linkconsulting.com <ju...@linkconsulting.com> #202
j....@old.faceit.com <j....@old.faceit.com> #203
je...@gmail.com <je...@gmail.com> #204
Please stop the useless "+1" messages as you spam a lot of people. People may un-star this issue because of your spam.... which is counterproductive.
Just give the bug/feature a star please!!
er...@gmail.com <er...@gmail.com> #205
wi...@gmail.com <wi...@gmail.com> #206
ss...@gmail.com <ss...@gmail.com> #207
co...@co3d.art <co...@co3d.art> #208
ha...@gmail.com <ha...@gmail.com> #209
[Deleted User] <[Deleted User]> #210
mo...@gmail.com <mo...@gmail.com> #211
ch...@gmail.com <ch...@gmail.com> #212
[Deleted User] <[Deleted User]> #213
si...@gmail.com <si...@gmail.com> #214
ne...@rakuten.com <ne...@rakuten.com> #215
de...@gmail.com <de...@gmail.com> #216
ir...@gmail.com <ir...@gmail.com> #217
+1
jb...@gmail.com <jb...@gmail.com> #218
If an issue is marked Fixed, no engineer is going to work on it. No one is even reading the updates.
Filing a new bug or finding an open bug is a better use of your time.
fu...@gmail.com <fu...@gmail.com> #219
[Deleted User] <[Deleted User]> #220
ca...@gmail.com <ca...@gmail.com> #221
ja...@mindforce.ai <ja...@mindforce.ai> #222
ha...@gmail.com <ha...@gmail.com> #223
+1
yo...@gmail.com <yo...@gmail.com> #224
ju...@gmail.com <ju...@gmail.com> #225
these emails for 13 years. Stop responding to this ticket!!
On Tue, Nov 2, 2021 at 8:17 PM <buganizer-system@google.com> wrote:
je...@gmail.com <je...@gmail.com> #226
ju...@gmail.com <ju...@gmail.com> #227
On Wed, Nov 3, 2021, 6:10 AM <buganizer-system@google.com> wrote:
me...@johnmann.org <me...@johnmann.org> #228
Select None from the list and it will unsubscribe you (see attached screenshot)
[Deleted User] <[Deleted User]> #229
h4...@gmail.com <h4...@gmail.com> #230
pu...@google.com <pu...@google.com> #231
Hello, can we have any updates regarding deletion of the App Engine? One of the customers is having their resources in the Europe region but they had created the App Engine in the us-west3 region. They need to have the App Engine in the Europe region as their services are hosted for that reason. Any updates on this would be really helpful.
le...@gmail.com <le...@gmail.com> #232
co...@pentech.io <co...@pentech.io> #233
ig...@getplutto.com <ig...@getplutto.com> #234
[Deleted User] <[Deleted User]> #235
[Deleted User] <[Deleted User]> #236
My use case is that
1. We're a huge org and creating a GCP project costs $20
2. I'm testing out terraform to provision gcp, including app engine
3. For development/testing purpose, I need to delete, reprovision and so on the whole infra including app engine; only the project remains there all the time
Since app engine app can't be deleted/modified, anytime I need to test something out, I have to create a project which is time & cost consuming
ra...@kxp.consulting <ra...@kxp.consulting> #237
Man, 14 years and nothing. This is very funny!
fc...@gmail.com <fc...@gmail.com> #238
ws...@gmail.com <ws...@gmail.com> #239
Just to be clear, I'm not asking for a refund. I just want to stop getting charged thousands of dollars for something that we don't use. This seems like the sort of problem that is caused by me being a longtime user of Google Cloud (since it was in private beta in 2014), and maybe the ability to disable app engine and stop getting charged in my case never got implemented.
According to the official docs at
I do have an open source ticket with Google about this, and was encouraged to post here as well to publicize this issue.
am...@google.com <am...@google.com> #240
our customer's App Engine is affected by this issue as well :
project ID : 817585749775 (sagetracwiki)
Org ID : 700484894011
App Engine : resource:gae_app
customer need to delete this App Engine , how we can help him on this ?
jb...@gmail.com <jb...@gmail.com> #241
as fixed and I assume no one will be looking at it.
On Thu, Sep 1, 2022 at 17:34 <buganizer-system@google.com> wrote:
fo...@gmail.com <fo...@gmail.com> #242
The same for me. My service was running on us-east-1 and went down almost 24h ago, because of lack of resources, and I'm trying the whole day to put my service up again, and I always receive the message: "An internal error occurred while processing task /app-engine-flex/flex_await_healthy/flex_await_healthy>2022-11-28T00:41:24.387Z123845.vt.1: The region us-east1 does not have enough resources available to fulfill the request. Please try again later."
Deleting a project and creating a new one would be very difficult as I have a lot of configuration and also a database in the same project. I can't change the zone of my app engine, neither delete it to create it again. What should I do?
I'm loosing many users because of that.
ch...@gmail.com <ch...@gmail.com> #243
ws...@gmail.com <ws...@gmail.com> #244
Yes, that was me. I was unable to get this fixed, and even now -- months later, I've still been paying ~$45/month for this. We are finally close to deleting this Google Cloud Project completely (since we switched to Github from self hosting), so for me this will soon finally be resolved. I am surprised by how this went, since expected somebody to just be able to edit something directly in a database to do a one-off fix for us, since that's how the analogous problem would definitely get solved for
In any case, I hope this gets solved for the sake of everybody else posting here.
ch...@gmail.com <ch...@gmail.com> #245
On Sun, Feb 26, 2023, 3:39 PM <buganizer-system@google.com> wrote:
gh...@google.com <gh...@google.com>
gh...@google.com <gh...@google.com> #246
As per the last comment provided by
or...@gmail.com <or...@gmail.com> #247
there are still hundredths of people waiting for a fix, please reopen it.
da...@gmail.com <da...@gmail.com> #248
On Wed 29 Mar 2023 at 07:55, <buganizer-system@google.com> wrote:
David Mc Gettigan
ha...@accenture.com <ha...@accenture.com> #249
2. Their "solution" is to delete the whole project, which is an unacceptable workaround.
3. If you are unable to reproduce the issue that must mean you are able to delete an App Engine application once it is deployed. Could you please provide the steps to do so? I you can't this issue is obviously still relevant.
jo...@gmail.com <jo...@gmail.com> #250
I was the “founder” of GCE at google and was there from the start as we created the idea of “project”. Note that it has been almost 10 years since I worked at google so ¯\_(ツ)_/¯. The Google Cloud project system was built so that project and GAE app were 1:1. You can tell because the name used for the GAE app and the project are the same and come out of the same namespace. (Fun fact: the GCS bucket names also come out of that namespace.)
I argued *strongly* at the time that project and GAE app project should be 1:n. Doing so would imply that you could create/delete many apps per project. But the app engine team, at the time, strongly advocated for how things end up and so here we are.
My guess — making project and GAE 1:n is almost impossible (or way to expensive) at this point. The only hope to “fixing” this bug would be to have something that can “reinitialize” a GAE app back to a blank state. My guess is if they did that it would (a) take a long time if there is a lot of data and (b) mean that you can’t use that project/app while it is deleting. And then there is the question about who pays the compute time necessary to do that deletion.
So I’d love to see them fix this but I wouldn’t hold my breath.
[Deleted User] <[Deleted User]> #251
ji...@googlemail.com <ji...@googlemail.com> #252
This is, in your whole product portfolio, the only resource which requires the whole project to be deleted.
That is a major design flaw, don’t you guys think?
vi...@rivile.lt <vi...@rivile.lt> #253
Why this ticket was closed? Please reopen. You can reproduce it any given day if you want.
g....@ferryhopper.com <g....@ferryhopper.com> #254
This is so frustrating. I wanted to play around with appengine, created a test app in a silly region that I cannot change, and now I'm stuck with it forever.
I guess
pe...@sumthing.org <pe...@sumthing.org> #255
Also, this ticket should be reopened.
yg...@ciandt.com <yg...@ciandt.com> #256
Can't believe this is actually a thing that has yet to be solved, lol
I guess I gotta be stuck to the App I created Ó╭╮Ò
Props to me for not using Cloud Run instead of AppEngine, dumbass
ch...@gmail.com <ch...@gmail.com> #257
After a decade, it's clear Google doesn't give a damn. How can I get off
the bug report?
On Thu, Oct 17, 2024 at 10:47 PM <buganizer-system@google.com> wrote:
Description
App Engine and possibly free up the name for another developer.