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

VM and VMSS validation fixes #6639

Merged
merged 3 commits into from Apr 30, 2020
Merged

VM and VMSS validation fixes #6639

merged 3 commits into from Apr 30, 2020

Conversation

manicminer
Copy link
Member

@manicminer manicminer commented Apr 27, 2020

Separate validation for VM/VMSS (resource) name, and linux/windows computer names

  • Adjust naming rules to meet current API behavior
  • Length validation for VMSS computer name prefixes

This maintains the current behavior of assuming the computer_name / computer_name_prefix from the VM / VMSS name respectively. However since the name values now have more relaxed rules, should the specified name not be a valid computer_name / computer_name_prefix, then the latter must also be specified. There are new tests for these cases.

…r names

- Adjust naming rules to meet current API behavior
- Length validation for VMSS computer name prefixes
@manicminer manicminer requested a review from a team April 27, 2020 12:44
@manicminer manicminer added the bug label Apr 27, 2020
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

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

Thanks @manicminer! Aside from some minor comments LGTM 👍

@katbyte katbyte added service/virtual-machine service/vmss Virtual Machine Scale Sets labels Apr 28, 2020
@katbyte katbyte added this to the v2.8.0 milestone Apr 28, 2020
@manicminer
Copy link
Member Author

Thanks @manicminer! Aside from some minor comments LGTM 👍

Fixed, thanks for catching!

@manicminer manicminer merged commit 15aac6a into master Apr 30, 2020
@manicminer manicminer deleted the vm-vmss-naming-validation branch April 30, 2020 16:12
manicminer added a commit that referenced this pull request Apr 30, 2020
@ghost
Copy link

ghost commented May 1, 2020

This has been released in version 2.8.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.8.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented May 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 👉 hashibot-feedback@hashicorp.com. Thanks!

@hashicorp hashicorp locked and limited conversation to collaborators May 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 this pull request may close these issues.

None yet

2 participants