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

Standardize google_compute_instance import #6023

Merged
merged 1 commit into from
Apr 6, 2020

Conversation

jcanseco
Copy link
Contributor

@jcanseco jcanseco commented Apr 1, 2020

This patch changes the import ID of google_compute_instance to have a
format that is more consistent with other resources like
google_compute_subnetwork while still supporting the previously
supported import ID of {{project}}/{{zone}}/{{name}} in order to have
backwards compatibility.

compute: Added more import formats for `google_compute_instance`

@ghost ghost added the size/xs label Apr 1, 2020
@ghost ghost requested review from emilymye April 1, 2020 13:34
@ghost ghost added the documentation label Apr 1, 2020
@emilymye emilymye changed the title Standardize google_compute_instance import ID Standardize google_compute_instance import Apr 1, 2020
@emilymye
Copy link
Contributor

emilymye commented Apr 1, 2020

Hi @jcanseco. Thanks for submitting! We'll go ahead and upstream this for you. In the future, if you want to do a similar change, it saves us a bit of work if you do so against MM. In this case, since instance is still a handwritten resource, it'd be these files.

Otherwise for autogenerated resources, it'd be in our terraform.yaml (see import_format, example) or inferred from the id format. Not sure if you might have already known, but just in case!

This patch changes the import ID of google_compute_instance to have a
format that is more consistent with other resources like
google_compute_subnetwork while still supporting the previously
supported import ID of {{project}}/{{zone}}/{{name}} in order to have
backwards compatibility.
@jcanseco
Copy link
Contributor Author

jcanseco commented Apr 1, 2020

Hi @emilymye thanks, the links are helpful. I'll make sure to apply changes to Magic Modules next time. In the meantime, I hope it's ok if I keep my last remaining PR open in this repo (I'm in the process of addressing its comments currently).

@ghost
Copy link

ghost commented May 7, 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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators May 7, 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.

None yet

3 participants