To do: use the environment's project ID - #365 (comment)

(Added label based on the heading...)

Just out of curiosity -- If I'm in App Engine, and want to talk to another project's datastore, and I do have the keyfile, can I still do that?

To put it another way, in App Engine, if I provide nothing to the code and just "hope that it figures it out", I'd want it to write to my App Engine app's datastore. I still want the ability to provide a specific set of credentials and a datastore/dataset ID (right now, this is equivalent to a project ID) and have my code talk outside my current app's dataset. Is that doable?

Just quickly looking at the PR here, it doesn't look like it gives us that option. If it detects that we are on GAE, it will automatically use those credentials to authorize the calls. It should definitely provide the option, i.e. if we provide configuration options, it will use those ALWAYS before defaulting to attempting GAE detection.

👍 to @ryanseys : I think we really need to make sure that code does the same thing across platforms.

If I manually configure my connection with a specific key, it should do the same thing on GCE as it does on GAE. It sounds like that isn't the case here.

@stephenplusplus : Can you take a look?

If a user provides configuration details, regardless of environment, that should definitely be honored (good catch!). It was overlooked in my original implementation, but I updated to support custom connection configuration never being precedented by magic.

#458 will squash this.

Coverage decreased (-39.9%) to 55.204% when pulling 0cf04ec on stephenplusplus:spp--gae into cd9487a on GoogleCloudPlatform:master.

@coveralls you're so weird.