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

google_compute_attached_disk doesn't work on regional persistent disks #2441

Closed
mcclunge opened this issue Nov 9, 2018 · 2 comments
Closed
Assignees
Labels

Comments

@mcclunge
Copy link

mcclunge commented Nov 9, 2018

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
  • If an issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.

Affected Resource(s)

  • google_compute_attached_disk

Expected Behavior

Be able to attach a regional persistent disk using google_compute_attached_disk

Actual Behavior

google_compute_attached_disk tries attaching a disk in the same zone as the instance it's trying to attach to.
Ex:
projects/{project-name}/zones/{zone-name}/disks/{disk-name}
Instead of:
projects/{project-name}/regions/{region}/disks/{disk-name}"

@ghost ghost added the bug label Nov 9, 2018
@mcclunge mcclunge changed the title google_compute_attached_disk doesn't work on regional persistent diskks google_compute_attached_disk doesn't work on regional persistent disks Nov 9, 2018
@chrisst chrisst self-assigned this Dec 5, 2018
@chrisst
Copy link
Contributor

chrisst commented Dec 7, 2018

Will be fixed in 2.0.0

@chrisst chrisst closed this as completed Dec 7, 2018
@ghost
Copy link

ghost commented Jan 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 Jan 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants