For our application (and I feel like most applications), if the datastore is unavailable, any action being performed will error with or without the other credentials. And if you use a fixed ID (or set) for the credentials and a caching persistence layer like Objectify, you'll likely have a copy of those credentials in Memcache and possibly the session cache.
Obviously, if you are less dependent on the datastore (or CloudSQL), that would make a difference from a design level. But for us, lacking access to the datastore makes access to external creds moot. On Monday, September 21, 2015 at 11:58:48 AM UTC-5, Frederik Creemers wrote: > > Hi Chad > > That's a nice solution to the problem, and it might be the best thing to > do given the current environment, but I don't like mixing > configuration/credentials management with the database layer. This would > mean that if the datastore is unavailable, I don't have access to my config. > > On Mon, Sep 21, 2015 at 4:52 PM Chad Vincent <[email protected] > <javascript:>> wrote: > >> We have a link to an external application, and just put the credentials >> (In this case, an API key with a matching username) in our User objects, >> and if it's a system-level event, it uses the key from the Administrator >> user. >> >> For anything that is global, we were just going to build an object in the >> Datastore that will be editable via our own Admin console. >> >> >> On Saturday, September 19, 2015 at 1:20:37 PM UTC-5, Frederik Creemers >> wrote: >>> >>> It's not good practice to store credentials in your source code >>> repository, but App Engine has no other way to inject these into your app. >>> Something like heroku's config variables would be great, or is there an >>> existing way to do this that I'm not aware of? >>> >> -- >> 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/PEfvmvSQOPY/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/b64e41da-8395-4b46-ae7b-e0e054c13d08%40googlegroups.com >> >> <https://groups.google.com/d/msgid/google-appengine/b64e41da-8395-4b46-ae7b-e0e054c13d08%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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/08613557-8da8-4350-8a5f-ee3e973a3251%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
