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

Change underscores to hyphens in google_compute_backend_service docs example #127

Merged

Conversation

rileykarson
Copy link
Collaborator

#40 got merged before I noticed the change from hyphens to underscores in the example in the docs; GCP resources names only allow hyphens as special characters and not underscores.

Update the .tf example and Import example to use hyphens.

@stack72
Copy link
Contributor

stack72 commented Jun 15, 2017

nice catch @rileykarson :)

@stack72 stack72 merged commit dae8662 into hashicorp:master Jun 15, 2017
pdecat pushed a commit to pdecat/terraform-provider-google that referenced this pull request Jun 29, 2017
…-example-underscores

Change underscores to hyphens in google_compute_backend_service docs example
chrisst pushed a commit to chrisst/terraform-provider-google that referenced this pull request Nov 9, 2018
…-example-underscores

Change underscores to hyphens in google_compute_backend_service docs example
luis-silva pushed a commit to luis-silva/terraform-provider-google that referenced this pull request May 21, 2019
@ghost
Copy link

ghost commented Mar 31, 2020

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 Mar 31, 2020
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