Thanks, Adam -- that's a big help! I'm making the changes to my workflow based on your suggestions and the related documentation, however the process has raised a few questions:
1) I haven't noticed dispatch.yaml mentioned in the new gcloud command documentation. Should this be included with the other yaml files for my default app? (app.yaml dos.yaml index.yaml) If I need to update just a service, (service1.yaml) should I include the default dispatch.yaml too? 2) Since the dispatch.yaml file applies to my entire project (both default app and services) if I update it alone with the gcloud command, is the --version flag ignored, or would it know to apply it just to my default project app, and not the individual version ids of the services? 3) Since the "version" id field is no longer used in the .yaml files, it appears that I can not update both my app and services in a single command AND include unique version ids for each with a single --version flag. In this case is it best practice to update the app and services individually so I can specify unique version ids for each? 4) While the "version" id field is no longer used in the .yaml files, the documentation suggests otherwise. On https://cloud.google.com/appengine/docs/python/tools/uploadinganapp under "Updating Indexes" it states, "Define a different version ID in your app's app.yaml file." Is this accurate or not? Any refinement you can offer on these issues would be very helpful. Brian On Saturday, December 31, 2016 at 6:00:54 PM UTC-6, Adam (Cloud Platform Support) wrote: > > Pre-release documentation can't be made available to the public > unfortunately. My recommendation is to read the current available App > Engine <https://cloud.google.com/appengine/docs>and gcloud docs > <https://cloud.google.com/sdk/gcloud/reference/app/deploy> and test. I > can list a few main differences here though: > > 1) New versions are promoted to receive all traffic by default. I'm of the > opinion that this is bad, and hopefully the default will change, but for > now you should disable this with the following command: > gcloud config set app/promote_by_default false > > 2) In your app.yaml and service .yaml files, the 'application: ' and > 'version: > ' fields are not used. You should set the project to deploy to with 'gcloud > config set project', and the version is automatically generated, or set > with the '--version=' flag to 'gcloud app deploy'. > > 3) You can use 'gcloud app deploy <deployable.yaml>' for any .yaml, such > as cron.yaml, dispatch.yaml and indexes.yaml. No need for separate > commands like update_indexes and update_dispatch. > > 4) For Java apps, everything is done using the new Gcloud Maven Plugin > <https://cloud.google.com/appengine/docs/java/tools/using-maven> which > handles translating the .xml config files to .yaml files for deployment. > It's similar to how the App Engine Maven Plugin worked on the standalone > SDK, but the plugin goals are different. > > 5) There is no vacuum_indexes command, instead you would use 'gcloud > preview datastore cleanup-indexes' > <https://cloud.google.com/sdk/gcloud/reference/preview/datastore/cleanup-indexes> > . > > On Saturday, December 31, 2016 at 11:20:12 AM UTC-5, Brian wrote: >> >> I just installed/updated my local gcloud SDK after a Ubuntu 14.04 to >> 16.04 upgrade. Apparently, appcfg is no longer available by default. I'd >> like to start using the preferred gcloud commands to manage my projects but >> I can't find an "appcfg" to "gcloud app deploy" migration guide anywhere. >> On Stack Overflow a while back, Zachary mentioned a migration guide >> <http://stackoverflow.com/questions/39280666/gcloud-app-deploy-vs-appcfg-py/39281006#> >> >> was planned. >> >> From what I've read, the changes look good, but there seems to be several >> gotchas that could really mess-up my active projects, so I would like to >> review the migration guide in fine detail to avoid any problems. >> >> Please let me know where I can find the migration guide so I can keep my >> projects moving forward. (At this point, even a rough draft would be very >> useful!) >> >> (I would have commented on the original Stack Overflow thread, but as a >> newbie there I'm not allowed because I don't have a high enough reputation >> yet.) >> > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/be5be774-beb9-4d88-a39d-4716e943b0d6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
