-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Container Engine clarifications #2142
Conversation
Environment variables should not be prefixed with dollar signs unless they are used explicitly in a bash command.
Clarify why we're using "_json_key" as the username. Properly indent steps within a deploy job.
gcloud --quiet config set project ${GOOGLE_PROJECT_ID} | ||
gcloud --quiet config set compute/zone ${GOOGLE_COMPUTE_ZONE} | ||
gcloud --quiet container clusters get-credentials ${GOOGLE_CLUSTER_NAME} | ||
``` | ||
|
||
|
||
Refer to the [Google Cloud](https://circleci.com/docs/2.0/deployment-integrations/#google-cloud) deploy example for further steps. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feels weird to link people to the rest of deploy section, when the page itself is called "deploying to", but its what the deployment-integrations page is for so w/e
LGTM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you!
Fixes #2134 and fixes #1670.
While working on this document, I realized a couple of things:
There is a lot of overlapping information between this document and the Authenticating Google Cloud document.
Both documents are mostly focused on steps preceding the actual deploy (authentication, environment variables, etc.).
The actual deploy instructions seem to be on the deploy landing page, but these seem to be a bit lean.
At the very least, we should consolidate Authenticating Google Cloud Platform and Deploying to Google Container Engine.
If we're feeling ambitious, I would pull all relevant Google Cloud setup documentation into a single document that is linked to from the Deploy landing page. The other deploy platforms could benefit from their own spaces as well.