[PATCH] Add appcfg.py convenience wrapper for google-cloud-sdk appengine component

[GoogleCodeExporter]

No straightforward way for SDK users to run appcfg.py for Google App Engine 
platform component.

What steps will reproduce the problem?:
- Install Google Cloud SDK and attempt to run 'appcfg.py'

What is the expected behaviour? What is the actual behaviour?:
- Actual behaviour is that appcfg.py is not found since it is not part of the 
PATH
- Expected behaviour should be the same as dev_appserver.py

Why does it happen?:
- Unlike dev_appserver.py, a convenience wrapper is missing for appcfg.py
- appcfg.py is not part of the PATH

What is the resolution?:
- Add a convenience wrapper for appcfg.py, similar to dev_appserver.py
- Give appcfg.py executable permissions (chmod +x)
- Patch attached; the file should be added to SDK_DIR/bin

What is the output of 'gcloud info'?:
- Attached

Original issue reported on code.google.com by hitster...@gmail.com on 8 Mar 2016 at 1:18

Attachments:

• appcfg.py.patch
• gcloud-sdk-98.log

[GoogleCodeExporter]

Thanks for the patch! This behavior is intended; it's harder for us to tell a 
coherent story about the future direction of App Engine tooling when we bundled 
a wrapper for appcfg.py.

If you would like to use appcfg.py, please install the App Engine SDK from 
here: https://cloud.google.com/appengine/downloads

For now, most users should use App Engine through the App Engine SDK; that's 
where most of our documentation points. If you would like to use the beta 
Managed VMs feature, or get a sneak peak of the new deployment experience, you 
may use the `gcloud preview app` family of commands included in the Cloud SDK.

Original comment by z...@google.com on 8 Mar 2016 at 1:24

• Changed state: WorkingAsIntended

[GoogleCodeExporter]

Thanks for your response. I will check out 'gcloud preview app' as per your 
suggestion.

Whilst I understand Google's position, it seems rather peculiar to provide the 
App Engine SDK as part of the Google Cloud SDK and whilst towing the App Engine 
SDK independently. More specifically updating the Cloud SDK unconditionally 
raises warnings that "outdated symlinks exist" if the App Engine SDK is already 
installed (as per your recommendation), even though the latter is NOT outdated 
when comparing versions. Moreover, it isn't clear how a coherent story is 
present if dev_appserver.py has a convenience wrapper but not appcfg.py. For 
seasoned Google Cloud Platform users, it's just one more thing to have to deal 
with, symlink'ing appcfg.py.

Unless I have entirely missed the point of your reply. :)

Original comment by hitster...@gmail.com on 9 Mar 2016 at 9:56