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

Generate new cmdlets for the first stable version of GA #18865

Merged

Conversation

arpit-gagneja
Copy link

Description

We have checked in the first stable version (GA) for swagger (Azure/azure-rest-api-specs#19553).
Based on this swagger, we want to create new cmdlets and ship new module for GA to our customers.

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • the markdown help files have been regenerated using the commands listed here

@arpit-gagneja arpit-gagneja assigned VeryEarly and unassigned VeryEarly Jul 4, 2022
@BethanyZhou
Copy link
Contributor

The PR looks good to me. If you want to GA Az.DnsResolver, please follow the GA process: https://github.com/Azure/azure-powershell-pr/wiki/Process-of-GA-module

@BethanyZhou BethanyZhou assigned BethanyZhou and unassigned VeryEarly Jul 6, 2022
@BethanyZhou BethanyZhou merged commit 4e6ff69 into Azure:generation Jul 6, 2022
@BethanyZhou BethanyZhou mentioned this pull request Jul 6, 2022
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants