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

Feature Request: Support the WriteAccelerator property on datadisks #959

Closed
anandramakrishna opened this issue Mar 9, 2018 · 12 comments · Fixed by #964
Closed

Feature Request: Support the WriteAccelerator property on datadisks #959

anandramakrishna opened this issue Mar 9, 2018 · 12 comments · Fixed by #964
Assignees
Labels
enhancement service/virtual-machine upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR
Milestone

Comments

@anandramakrishna
Copy link

anandramakrishna commented Mar 9, 2018

Affected Resource(s)

  • azurerm_compute_virtual_machine

References

See azure-sdk-for-go/services/compute/mgmt/2017-12-01/compute/models.go for information about the WriteAccelerator property.

@anandramakrishna
Copy link
Author

@katbyte I was reviewing your PR and observed that this is set to default to "true". I don't think that's correct, as that would be a change for existing terraform deployments.

We should make the default be "false" for this .

@katbyte
Copy link
Collaborator

katbyte commented Mar 13, 2018

Hi @anandramakrishna,

Thank you for taking a look 🙂

Currently the property is optional, so I believe if it is left out it will be false and not enable the feature. Currently I can not fully test this PR as it is in public preview and I don't think our subscription is whitelisted, I haven't checked yet.

@anandramakrishna
Copy link
Author

I can get your subscription whitelisted if necessary. Please let me (or others at MS) know which one.

@tombuildsstuff
Copy link
Contributor

@anandramakrishna based on your message, is this functionality invite-only at this point; or can users self-register for it?

@anandramakrishna
Copy link
Author

Let me follow-up on this. I'll get back to you.

@anandramakrishna
Copy link
Author

I've enabled your subscription. Users will be able to use it publicly without needing whitelisting in another week (approximately).

@katbyte
Copy link
Collaborator

katbyte commented May 7, 2018

Hey @anandramakrishna,

Just wanted to provide an update: We are currently waiting for capacity on our subscription so we can test and run acceptance tests. Once we have quote and can verify everything works as expected we can merge an close this out.

@katbyte katbyte added this to the Future milestone May 7, 2018
@tombuildsstuff tombuildsstuff added the upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR label May 11, 2018
@BalaAnbalagan
Copy link

Hi
Please let me know how to use it, I can test it.

@katbyte
Copy link
Collaborator

katbyte commented May 12, 2018

Hi @BAnbalagan,

Thank you for the offer but not only do we need confirm it works, we need a way to continuously test it going forward as changes are made to the resource.

@katbyte katbyte modified the milestones: Future, 1.7.0 May 25, 2018
@katbyte
Copy link
Collaborator

katbyte commented Jun 16, 2018

Hey @anandramakrishna, @BalaAnbalagan,

Just wanted to let you know this has been included in 1.7 and releases today.

@BalaAnbalagan
Copy link

BalaAnbalagan commented Jun 16, 2018 via email

@ghost
Copy link

ghost commented Mar 30, 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 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement service/virtual-machine upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR
Projects
None yet
5 participants