Deleted default Google Cloud Storage bucket, unable to recreate

1,942 views
Skip to first unread message

Sean Lynch

unread,
Jun 8, 2015, 4:00:39 PM6/8/15
to google-a...@googlegroups.com
While attempting to get the ACL setup correctly on the default Google Cloud Storage bucket (APPID.appspot.com), I deleted this default bucket but now I see no way to recreate it.  

Under Cloud Integration on the old App Engine console, I now see "The project was created successfully. See the Basics section for more details." instead of the create button.  At the top of Application Settings I see Google Cloud Storage Bucket: APPID.appspot.com but clicking the link returns "A required resource is not available".

I tried to manually recreate the GCS bucket under the new Cloud console, but get the error:
Note that a bucket name may only contain a dot if it is a valid domain name, such as "example.com" or "sub.example.com". You will need to demonstrate that you are an owner or manager of this domain before creating the bucket.

I'd rather not create a new application to replace this one.  How can I recreate the default bucket? 

Patrice (Cloud Platform Support)

unread,
Jun 8, 2015, 5:38:23 PM6/8/15
to google-a...@googlegroups.com, tech...@gmail.com
Hi Sean,

Unfortunately, no there is no way to re-create the default bucket if you deleted it. 

I don't see why you really need the default one though... can't you use any other bucket, since they have the exact same behavior as the default ones?

If you really need to use the default one, yes unfortunately the only way to do so is to re-create a new app, but again, I don't see why you need to take the default one, when you can just create a new one.

Cheers!

Jeff Schnitzer

unread,
Jun 8, 2015, 6:20:42 PM6/8/15
to Google App Engine
While I haven't made this particular mistake, it's actually kind of a big deal. We deploy the same code to acceptance, staging, etc environments. Using the default bucket means we don't have to set up buckets by hand for each of those environments. Before you say "that's not a big deal", the entire career of devops exists because there are a thousand "no big deals" required to set up and run environments. GAE's primary value proposition is "no devops".

Also, it's just very bad practice to have buttons that, when accidentally clicked, wedge the application into a state that cannot be recovered without spending engineering resources on changing the deployment process.

I would star this issue.

Jeff

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/4c503d36-706c-4cbe-ba70-984b529c856f%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Sean Lynch

unread,
Jun 8, 2015, 7:09:23 PM6/8/15
to Google App Engine

While GCS is very cheap, the default bucket is free up to 5GB and more importantly, does not require billing to be enabled. I just ported an application using the deprecated google.appengine.ext.files API to GCS but now I'll need to enable billing to restore this file upload functionality for their application.


You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/Bq9TeY1f3kM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.

To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.

Chris Ramsdale

unread,
Jun 8, 2015, 11:55:48 PM6/8/15
to google-a...@googlegroups.com
well, this isn't cool.  let me look into what's going on here and see if we can add a fix.  at minimum, we shouldn't allow you to delete the default bucket (we use if for other services) and get yourself into a horked state.  -- Chris

bb b

unread,
Nov 1, 2015, 6:08:01 AM11/1/15
to Google App Engine
Reviving this thread... Is there a tracker for this issue?

I ran into a different version of this: I accidentally deleted the staging.<app-name>.appspot.com bucket used by the Managed VM deployment process (gcloud preview app deploy) and I can't recreate it; further invocations of "gcloud preview app deploy" fail when trying to add files to this bucket. As far as I know there's no way to change the staging bucket used by that deployment process, so it would seem that I can't use Managed VM in this project anymore. :-(

+1 to Jeff Schnitzer's "it's just very bad practice to have buttons that, when accidentally clicked, wedge the application into a state that cannot be recovered without spending engineering resources on changing the deployment process"

bb b

unread,
Nov 1, 2015, 6:39:40 AM11/1/15
to Google App Engine
Filed https://code.google.com/p/googleappengine/issues/detail?id=12502 for the issue specific to Managed VMs.
Reply all
Reply to author
Forward
0 new messages