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

(#14906) docs/provider/azure/vmss: managed_disk_type, typos; sidebar fix VM #14915

Merged
merged 1 commit into from
May 30, 2017

Conversation

ebrucucen
Copy link
Contributor

a. [vmss.markdown]

  • As mentioned on Azure VMSS documentation corrections #14906, For storage_profile_os_disk, when managed_disk_type is specified, the name attribute should have been "" (blank), fixed on the example and the explanation.
  • Added hcl for the managed disk example syntax.
  • Virtual Machine Scale Sets -> Virtual Machine Scale Set [made singular]
    b. [azurerm.erb]
  • Sidebar fix: "virtualmachine" was confusing the other links, so set the VM sidebar link as "virtual-machine" and rest of all as "virtualmachine-xyz"; top level as "virtual"
  • Virtual Machine Scale Sets -> Virtual Machine Scale Set [made singular]

Copy link
Contributor

@tombuildsstuff tombuildsstuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @ebrucucen

Thanks for this PR - I've taken a look and this LGTM :)

I've also opened #14932 to discuss making name an optional field, rather than an empty string.

Thanks!

@@ -327,7 +325,7 @@ The following arguments are supported:

`storage_profile_os_disk` supports the following:

* `name` - (Required) Specifies the disk name.
* `name` - (Required) Specifies the disk name. Value must be blank (`""`) when `managed_disk_type` is specified.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Related: I've opened issue #14932 to discuss making this field Optional, so this is no longer needed

@ghost
Copy link

ghost commented Apr 11, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants