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

virtual machine contributor: map to classic rather than ARM #670

Closed
JasonNguyenTX opened this issue Jan 8, 2018 · 2 comments · Fixed by #762
Closed

virtual machine contributor: map to classic rather than ARM #670

JasonNguyenTX opened this issue Jan 8, 2018 · 2 comments · Fixed by #762
Assignees
Milestone

Comments

@JasonNguyenTX
Copy link

Virtual Machine Contributor role currently maps to classic virtual machine contributor. Is there a plan to update it to ARM virtual machine contributor role?

@tombuildsstuff tombuildsstuff added this to the 1.0.2 milestone Jan 16, 2018
@tombuildsstuff
Copy link
Contributor

hey @JasonNguyenTX

Thanks for opening this issue

I've replicated this and we'll fix this in the next release of the AzureRM Provider, the correct GUID for for the Virtual Machine Contributor role is 9980e02c-c2be-4d73-94e8-173b1dc7cf3c.

Thanks!

@tombuildsstuff tombuildsstuff self-assigned this Jan 16, 2018
@tombuildsstuff tombuildsstuff modified the milestones: 1.0.2, 1.0.3 Jan 26, 2018
@tombuildsstuff tombuildsstuff modified the milestones: 1.1.1, 1.1.0 Feb 6, 2018
@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 a pull request may close this issue.

2 participants