-
Notifications
You must be signed in to change notification settings - Fork 336
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
Add support for write_accelerator_enabled
#1808
base: dev
Are you sure you want to change the base?
Add support for write_accelerator_enabled
#1808
Conversation
write_accelerator_enabled
@Fred-sun thanks for your work, here are my tests: First I create a disk with the Azure.Azcollection Collection 3.1.0: Playbook - need to set environment variables before and replace '':
Works, output looks like this:
executing it a second time (testing idempotence):
Well, let's ignore that for now, seems like another Bug/Issue. I implement your changes and try from the start, playbook is the same, i just uncomment the "write_accelerator_enabled: True"-line. I've removed the disk manually in the Azure Portal inbetween. First run:
The disk is created and attached successfully to a VM, with Write Accelerator enabled, shown in the Azure Portal: However, the _info module misses the caching and the write_accelerator information.
Output:
While this shows the caching information, it doesn't show the write_accelerator information. |
@unkaputtbar112 I have updated, Please take a try! Thanks! |
@Fred-sun thanks a lot for your work. :) Now it works just fine, the output of azure_rm_virtualmachine_info looks now like this:
Just for reference, for the issue of re-running / changing "attach_caching" i've created following issue: |
SUMMARY
Add support 'write_accelerator_enabled', try to fixes #430, #1811
ISSUE TYPE
COMPONENT NAME
azure_rm_manageddisk.py
azure_rm_virtualmachine.py
ADDITIONAL INFORMATION