Skip to content

Domain name label with randomness for New-AzureRMVM and VMSS. #5399

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

Merged
merged 16 commits into from
Feb 7, 2018
Merged

Domain name label with randomness for New-AzureRMVM and VMSS. #5399

merged 16 commits into from
Feb 7, 2018

Conversation

sergey-shandar
Copy link
Contributor

@sergey-shandar sergey-shandar commented Jan 31, 2018

Description

Domain name randomness.

  • Note: Before merging we need to fix VMSS output to print generated domain name.

This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

General Guidelines

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
  • The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

  • Pull request includes test coverage for the included changes.
  • PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

  • New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
  • Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

  • Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
  • Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
  • Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

@sergey-shandar sergey-shandar changed the title Domain name label with randomness. [Do Not Merge yet] Domain name label with randomness. Jan 31, 2018
twitchax
twitchax previously approved these changes Jan 31, 2018
Copy link
Contributor

@twitchax twitchax left a comment

Choose a reason for hiding this comment

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

LGTM.

do
{
domainNameLabel.Value = (name + '-' + Guid.NewGuid().ToString().Substring(0, 6)).ToLower();
} while ((await networkClient.CheckDnsNameAvailabilityAsync(location, domainNameLabel.Value)).Available != true);
Copy link
Contributor

Choose a reason for hiding this comment

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

Instead of != true, just throw a ! out front?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is bool? so I would like to have explicit syntax.

@sergey-shandar sergey-shandar changed the title [Do Not Merge yet] Domain name label with randomness. Domain name label with randomness. Feb 1, 2018
@sergey-shandar sergey-shandar changed the title Domain name label with randomness. Domain name label with randomness for New-AzureRMVM and VMSS. Feb 1, 2018
@sergey-shandar sergey-shandar changed the title Domain name label with randomness for New-AzureRMVM and VMSS. [Do not merge] Domain name label with randomness for New-AzureRMVM and VMSS. Feb 2, 2018
@sergey-shandar sergey-shandar changed the title [Do not merge] Domain name label with randomness for New-AzureRMVM and VMSS. Domain name label with randomness for New-AzureRMVM and VMSS. Feb 2, 2018
@sergey-shandar
Copy link
Contributor Author

sergey-shandar commented Feb 2, 2018

Ready for review.

Copy link
Member

@markcowl markcowl left a comment

Choose a reason for hiding this comment

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

Please file an issue to add domain name label validation to existing VM tests

@markcowl markcowl removed their assignment Feb 3, 2018
@markcowl
Copy link
Member

markcowl commented Feb 3, 2018

Copy link
Member

@markcowl markcowl left a comment

Choose a reason for hiding this comment

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

The test for simple vm parameter set is failing in the on-demand runbecause it needs to be re-recorded.

Also, please mark this as a check-in test

markcowl
markcowl previously approved these changes Feb 5, 2018
@sergey-shandar
Copy link
Contributor Author

#5451

@markcowl
Copy link
Member

markcowl commented Feb 6, 2018

@markcowl markcowl changed the base branch from preview to release-2018-02-09 February 6, 2018 03:37
@markcowl
Copy link
Member

markcowl commented Feb 6, 2018

@markcowl markcowl merged commit 44f20d8 into Azure:release-2018-02-09 Feb 7, 2018
@sergey-shandar sergey-shandar deleted the sergey-domain-name-fix branch February 7, 2018 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants