Completely removing an application

[Mark Betz]

Hi guys. We have a couple of Google projects that we work in and today I accidentally deployed a set of Google App Engine modules into a project where we only want to run some container engine stuff. I haven't been able to figure out how to remove them. The version for all of them is 'beta-1' but if I do...

appcfg.py delete_version -A <app id> -V beta-1

I get an error "Cannot delete default version of default module."

Is there no way to simply remove this deployment?

On a related note, and so I don't step on my own foot again, can anyone clarify the relationship between Google Cloud projects and Google App Engine applications? I have the Google cloud SDK installed, and at any given time that is set to some default one of our cloud projects. However the appcfg.py tool doesn't seem to have an option to specific which project I want stuff deployed into. Do deployments always go into the default project? Or is it related somehow to the application id that you choose?

Thanks for any help!

--Mark

[Christian F. Howes]

mark,

since the move to console.developers.google.com i have not deleted an app engine module fully.  but at appengine.google.com you can delete versions of a an app engine module.  once all non-default versions are deleted it should let you delete the default version (at least it did the last time i did it).  i haven't tried to delete a module from appcfg.py

cloud projects as i understand them...  each GAE application ID is associated with a cloud project.  so i think that the app ID that appcfg.py uses is a one to one mapping to cloud project ID.  hopefully someone will correct me if i'm wrong.

cfh

[Adam]

Unfortunately you cannot delete the default version on app from the old console either (You'll see the message "Cannot delete default version."). If you can't lose the project the best option is to just deploy a dummy app as the new default (eg. an app that does nothing, or serves a single blank static file - you need to define at least one URL handler for the deploy to work).

[Mark Betz]

Thanks for the responses, guys. I'm pretty amazed that there isn't some straight-forward way to blow away the deployment and start over, short of ditching the project and whatever other resources have been set up in it (datastore, cloudQL, network rules, etc.). 

Appreciate the help. Our CTO wanted us to look at this platform as a potential alternative to Google Container Engine, but this is a deal-breaker for me.

On Friday, December 11, 2015 at 7:01:50 PM UTC-5, Mark Betz wrote:

[Christian F. Howes]

I'm confused. you can indeed start over with your GAE deployments.  each deploy replaces what is there, and even if the default version of the default module can't be deleted it doesn't cost you anything if nothing accesses it.  just deploy new code and you are good to go.

See notes on deploying and deleting individual modules here: https://cloud.google.com/appengine/docs/python/modules/#Python_Uploading_modules

[Mark Betz]

Christian, it's probably a lack of trust on my part, but I don't like any of what you've described there :). Most of my experience on the Google Platform is with container engine, and what I want from app engine is that I can do the same thing I can do in container engine when I delete a cluster or remove an image from the registry: it's gone. I think pretty much everyone expects standard CRUD behavior to be possible with all cloud resources, i.e. anything I can create I can completely remove. It doesn't seem like an odd or confusing idea to me.

--
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/Hkn81G5Gr-A/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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/c1690f03-821f-428b-9789-5abfd22efcd0%40googlegroups.com.

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

--

Mark Betz

Sr. Software Engineer

icitizen

Email: mark...@icitizen.com

Twitter: @markbetz

[Barry Hunter]

 

appcfg.py delete_version -A <app id> -V beta-1

I get an error "Cannot delete default version of default module."

Is there no way to simply remove this deployment?

I think you saying you dont need AppEngine for this project at all? 

So could just delete the App Engine App. Or disable it - So it wont run. 

(but not the Cloud Project, still need that!)  

 

... of if really paranoid, deploy a new 'empty' module. Make it the default, and delete the other module. 

 

 can anyone clarify the relationship between Google Cloud projects and Google App Engine applications?

Its a one-to-one mapping in my experience. Each AppEngine app got a Cloud project. If you create a Cloud project, there is automatically a App Engine AppID for it. 

 

Or is it related somehow to the application id that you choose?

Yes. 

[Mark Betz]

Yes, we basically don't want the GAE code in that project at all. What happened is that a deploy script was run without a command line arg specifying the project, and took the current default gcloud project and used that. That was all totally our fault and we can prevent it happening again with changes to the tooling. Not being able to simply remove the accidentally-deployed code is the part that bothers me. That's just a lot less control than I am used to having over an environment. To be fair I don't have a lot of experience with PAAS offerings, so I can't say whether, for example, you can easily remove deployed code on Heroku or other platforms, but it doesn't seem like an odd thing to want to do.

On Friday, December 11, 2015 at 7:01:50 PM UTC-5, Mark Betz wrote:

[Yordis Prieto]

I know has been long time but I agree with you Mark. I wan't that default service from the App Engine to disappear all at once

On Friday, December 11, 2015 at 7:01:50 PM UTC-5, Mark Betz wrote:

[Jason Keene]

I agree, it is highly annoying that you can not delete the service without deleting the entire project. Sad.

[Hamish Wadham]

Totally agree. I too am looking at alternatives to AWS which we currently use. If you don't need something it needs to be removable.

I too am cautious of some costs sneaking in.