Craig, We should probably look at making this a real feature. The configuration isn't the best solution because it means you need to swap the config in and out between deploys. It also means that if you want to restrict access to a staging version, you won't be able to just click the dashboard to switch versions after a deploy or rollback.
If you're using Java, it might even be better to create a filter that detects the request URI and forcing an admin login. You can programmatically detect the version, but again, this breaks your ability to deploy/rollback without a change: http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/utils/SystemProperty.html Unless you store the current version in Memcache and do a check each time ... again, not a great solution. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Wed, Jul 20, 2011 at 10:32 PM, Craig <[email protected]> wrote: > I was thinking of something to click in the admin web console, but making > the configuration change will certainly do it - I didn't think of doing it > that way. Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/VsxuIjOkdrwJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
