The password depreciation breaks my workflow at extremes 1) I have an old project with a dedicated and modified old SDK, I'm not sure whether an updated SDK would be able to accommodate that project 2) I'm unsure how the new deploy command works, at the very least, a forced SDK update breaks my new workflow too, as I have to manually modify the SDK I use to mend the shortcomings and various bugs
I guess a logical solution for both issues to use a third SDK, just for deployments - assuming it's still possible to deploy from the CLI Out of curiosity, how much does the oauth workflow increase the security - isn't the existing password routine secure? Or is it just there to ensure the SDK password routine is compatible with the rest of the google password routines and it's too much of an effort to keep the existing routine? -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/b46654bb-7dce-42ed-a08a-9dc05865c014%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
