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

Move shared gallery to stable folder, and update blob as source template #12442

Merged

Conversation

kangsun-ctrl
Copy link
Contributor

@kangsun-ctrl kangsun-ctrl commented Jan 15, 2021

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Changelog

Please ensure to add changelog with this PR by answering the following questions.

  1. What's the purpose of the update?
    • new service onboarding
    • new API version
    • update existing version for new feature
    • update existing version to fix swagger quality issue in s360
    • Other, please clarify
  2. When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
  3. When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
  4. If it's an update to existing version, please select SDKs of specific language and CLIs that require refresh after swagger is published.
    • SDK of .NET (need service team to ensure code readiness)
    • SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • PowerShell
    • CLI
    • Terraform
    • No, no need to refresh for updates in this PR

Contribution checklist:

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

  • Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

    • Adding new API(s)
    • Adding a new API version
    • Adding a new service
  • Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

  • If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in stable version
  • Removing properties in stable version
  • Removing API version(s) in stable version
  • Updating API in stable version with Breaking Change Validation errors
  • Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.

Please follow the link to find more details on PR review process.

@kangsun-ctrl
Copy link
Contributor Author

kangsun-ctrl commented Mar 5, 2021

changelist1: https://github.com/Azure/azure-rest-api-specs/pull/12442/files/eb058531c2c818aa0ef3b13b0202fd6608cd1188

After that, I recovered files for preview/2020-09-30
@Sandido

@JeffreyRichter JeffreyRichter added the Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 label Mar 12, 2021
@Sandido
Copy link
Member

Sandido commented Mar 12, 2021

@kangsun-ctrl , please link the .NEt SDK PR for these changes.

@kangsun-ctrl
Copy link
Contributor Author

SDK pr link: Azure/azure-sdk-for-net#19472

@kangsun-ctrl kangsun-ctrl merged commit 6bb9742 into Azure:compute-2021-03 Mar 16, 2021
grizzlytheodore added a commit that referenced this pull request Mar 25, 2021
grizzlytheodore added a commit that referenced this pull request Mar 25, 2021
grizzlytheodore pushed a commit that referenced this pull request Apr 5, 2021
…ate (#12442)

* add new api version 2020-09-30 for gallery.json

* add support for api change, sharing profile related

* update, change post to patch

* fix model validation error

* fix typo

* add shared gallery api

* update

* fix typo

* update

* update

* update

* chagne new api version to preview

* update readme.md and nit

* remove some required field and make groups readonly

* add swagger support for Grace's and Tim's work

* error fix

* error fix

* change api version name to 2020-09-30 withour 'preview'

* update

* fix typo

* address pr comment

* set modelAsString to true for gallery sharing-related enum

* update, fix merge

* remove duplicate entry

* shared gallery, change id to identifier.uniqueId

* fix typo

* update, remove x-ms-azure-resource for shared gallery

* change name of Permissions to avoid SDK code build error

* update

* add new line

* move all 2020-09-30 shared gallery api version to stable

* update blob as source template and example

* add example that user can update sig image without source id

* update get sig version with vhd source

* update readme.md

* update files after prettier check

* update azureresourceschema.md

* update typo

* resolve breaking change

* address comments

* include gallery example change

* add stable/2020-09-30/gallery and sharedGallery to readme file

* nit

* address comment
grizzlytheodore added a commit that referenced this pull request Apr 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 CI-BreakingChange-Go CI-BreakingChange-Python FixS360
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants