Is there a better way to set a gcloud project in a directory? : <p>I work on multiple appengine projects in any given week. i.e. assume multiple clients. Earlier I could set <code>application</code> in <code>app.yaml</code>. So whenever I did <code>appcfg.py update....</code> it would ensure deployment to the right project.</p>

<p>When deploying, the application variable throws an error with <code>gcloud deploy</code>. I had to use 
<code>gcloud app deploy --project [YOUR_PROJECT_ID]</code>. So what used to be a directory level setting for a project, is now going into our build tooling. And missing out that simple detail can push a project code to the wrong customer. 
i.e. if I did <code>gcloud config set project proj1</code> and then somehow did a <code>gcloud app deploy</code> in proj2, it would deploy to proj1. Production deployments are done after detailed verification on the build tools and hence it is less of an issue there because we still use the <code>--project</code> flag.</p>

<p>But its hard to do similar stuff on the development environment. <code>dev_appserver.py</code> doesn't have a <code>--project</code> flag.
When starting <code>dev_appserver.py</code> I've to do <code>gcloud config set project &lt;project-id&gt;</code> before I start the server. This is important when I using stuff like PubSub or GCS (in dev topics or dev buckets). </p>

<p>Unfortunately, missing out a simple configuration like setting a project ID in a dev environment can result into uploading blobs/messages/etc into the wrong dev gcs bucket or wrong dev pubsub topic (not using emulators). And this has happened quite a few times especially when starting new projects.</p>

<p>I find the above solutions as hackish-workarounds. Is there a good way to ensure that we do not deploy or develop in a wrong project when working from a certain directory?</p>
