Skip to content

Remove ValidateSet to allow newly introduced auxiliarySkus on the nic#29301

Open
pr-work wants to merge 3 commits intoAzure:release-network-2025-07-01from
pr-work:prbhavsar/removeValidateSet2
Open

Remove ValidateSet to allow newly introduced auxiliarySkus on the nic#29301
pr-work wants to merge 3 commits intoAzure:release-network-2025-07-01from
pr-work:prbhavsar/removeValidateSet2

Conversation

@pr-work
Copy link
Copy Markdown
Member

@pr-work pr-work commented Mar 23, 2026

Description

Remove ValidateSet for auxiliarySku parameter on NetworkInterface
Remove the ValidateSet constraint from the New-NetworkInterfaceCommand to allow newly introduced auxiliary SKUs without requiring explicit updates to PowerShell, CLI, and other client tools.
As new auxiliary SKUs are being introduced at an increasingly rapid pace, the current approach of updating the ValidateSet for each new SKU creates unnecessary delays in customer onboarding. Removing this client-side validation streamlines the process, as server-side validations already enforce valid SKU values and will reject invalid inputs.

Mandatory Checklist

  • SHOULD update ChangeLog.md file(s) appropriately
    • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
      • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT adjust version of module manually in pull request

@azure-client-tools-bot-prd
Copy link
Copy Markdown

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

@NoriZC
Copy link
Copy Markdown
Contributor

NoriZC commented Mar 23, 2026

/azp run

@azure-pipelines
Copy link
Copy Markdown
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@pr-work pr-work requested a review from berndverst March 24, 2026 16:38
@NoriZC NoriZC self-assigned this Mar 25, 2026
@NoriZC
Copy link
Copy Markdown
Contributor

NoriZC commented Mar 25, 2026

/azp run

@azure-pipelines
Copy link
Copy Markdown
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@VeryEarly
Copy link
Copy Markdown
Collaborator

@NoriZC
Copy link
Copy Markdown
Contributor

NoriZC commented Mar 27, 2026

@pr-work Could you please address the comment above?

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.

3 participants