Skip to content
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

Explain why scopes are required #3116

Conversation

conorgil
Copy link
Contributor

Scopes are the legacy way to assign permissions
to an instance, so it was incredibly confusing
for a first time GCP user why this field is required.

This updates the terraform docs to explain this briefly
and link to the Google docs which state that this field
is still required (presumably, for legacy reasons).

Scopes are the legacy way to assign permissions
to an instance, so it was incredibly confusing
for a first time GCP user why this field was required.

This updates the terraform docs to explain this briefly
and link to the Google docs which state that this field
is still required  (presumably, for legacy reasons).
Copy link
Collaborator

@rileykarson rileykarson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for clarifying this @conorgil!

@rileykarson rileykarson merged commit c49323a into hashicorp:master Mar 7, 2019
@conorgil conorgil deleted the docs/compute_instance_template_service_account_scopes branch March 14, 2019 00:42
@ghost
Copy link

ghost commented Apr 7, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants