[Hub Generated] Add Microsoft.AppPlatform/Spring new pricing tier on API version 2022-01-01-preview #17141
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* fix swagger of build service * fix
Co-authored-by: Xiaoyun Ding <xiading@microsoft.com>
* Change appName to appResourceId * fix
* Change appName to appResourceId * rename sourceGateways to gatewayIds * Change operatorRuntimeState to resourceRequest
yuwzho
requested review from
ArcturusZhang,
BigCat20196,
msyyc and
RAY-316
as code owners
|
The PR is created based on the updates in the private branch. The updates in the PR has already been reviewed and approved with this PR Azure/azure-rest-api-specs-pr/4120 |
|
Hi, @yuwzho Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com |
This was referenced Dec 20, 2021
This was referenced Dec 20, 2021
|
@ArcturusZhang @msyyc , the cross version breaking change was approved in associated PR at private repo. Can you approve from SDK perspective? |
25 tasks
yuwzho
changed the title
raych1
approved these changes
Dec 22, 2021
This was referenced Dec 22, 2021
ghost
pushed a commit
to Azure/azure-resource-manager-schemas
that referenced
this pull request
Dec 22, 2021
…ing new pricing tier on API version 2022-01-01-preview (#2112) Create to sync Azure/azure-rest-api-specs#17141 [ReCreate this PR](https://github.com/azure-resource-manager-schemas/compare/main...AzureSDKAutomation:sdkAuto/appplatform?expand=1)
26 tasks
LeiWang3
pushed a commit
to LeiWang3/azure-rest-api-specs
that referenced
this pull request
Mar 31, 2022
…API version 2022-01-01-preview (Azure#17141) * copy from last api version * Add system data and example * Add availability zones change * Configuration Service * Service Registry * Gateway * API portal * App and Deployment * BuildServices/Builds/Builders/BuildResults * BuildPackBindings * fix swagger of build service (Azure#43) * fix swagger of build service * fix * fix: add agentPool in BuildProperties (Azure#44) * Add fqdn in service resource (Azure#45) Co-authored-by: Xiaoyun Ding <xiading@microsoft.com> * Change appName to appResourceId (Azure#46) * Change appName to appResourceId * fix * Add resource id to connect resources * Change operatorRuntimeState to resourceRequest (Azure#49) * Change appName to appResourceId * rename sourceGateways to gatewayIds * Change operatorRuntimeState to resourceRequest * feat: update agent pool swagger (Azure#50) * Update 201 descriptions about header * add get build (Azure#51) * Remove 202 for PUT * List and Get supportedBuildpacks * set active deployment should be async * Update setActiveDeployments response body * ContentCertificateProperties.content should be secret * Add jvmOptions for Jar type Co-authored-by: Qingyi Liu <34502364+smile37773@users.noreply.github.com> Co-authored-by: Xiaoyun Ding <leonard520@users.noreply.github.com> Co-authored-by: Xiaoyun Ding <xiading@microsoft.com> Co-authored-by: ninpan-ms <71061174+ninpan-ms@users.noreply.github.com> Co-authored-by: zhoufenqin <fenzho@microsoft.com>
JackTn
deleted the
published/VSChina/azure-rest-api-specs-pr/yuwzho/appplatform-2021-08-01-preview
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.
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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
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.