-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Importing google_dns_managed_zone with project #1944
Conversation
- added tests and acceptance tests
or by using `project-id` and `name` e.g. | ||
|
||
``` | ||
$ terraform import google_dns_managed_zone.foo project/managedZones/foo-zone |
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.
nitpick: could we maybe use project-id
instead of project
, to make it clear that project
isn't a hardcoded string, and to match the description?
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.
Sorry for the delay.
Sure. I documented all import formats like on compute disk using project-id
Importing google_dns_managed_zone with project
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! |
importing Cloud DNS managed zones from a different project.
Any comments are welcome. Esp. on doing acceptance tests with a different project are very welcome.
See also #1676