-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Release Microsoft.App 2022-11-01-preview #22896
Conversation
…preview to version 2022-10-01
…o version 2022-11-01-preview
* Add new props * add defaults
…review (Azure#21464) * fix * fix
* Remove AppState property as we decided to postpone it * Fix swagger issues * fix swagger issues * More swagger fixes * Swagger fixes * additional fix * Even more swagger fixes - where does this come from? * Fix other swagger issues * fixing remaining swagger issues
* fix S360 swagger correctness errors * add default value Co-authored-by: Nan Jiang <naji@microsoft.com>
* Add swagger for client cert & CORS policy (Azure#21126) * Add certificate & CORS Policy * try fix
* {AzureContainerApps} fixes Azure#21354 runtimeSubnetId was the old way of doing it and now it is no longer needed. It is very confusing to still see it being used or required in API specification documentation below: https://learn.microsoft.com/en-us/azure/templates/microsoft.app/managedenvironments?pivots=deployment-language-bicep#vnetconfiguration This PR updates the description mentioning it is deprecated. * Update ManagedEnvironments.json * Update ManagedEnvironments.json * Update ManagedEnvironments.json * Update ManagedEnvironments.json
* add managed cert API in 2022-11-01-preview * prettierred Co-authored-by: Elle Tojaroon <patojaro@microsoft.com>
Co-authored-by: Vincent He <dashe@microsoft.com>
* add sticky sessions first commit * add examples * fix semantic validation * remove breaking sdk error's duplicates * fix camelCase error * remove extra attributes * change affinity property to a string enum * change Sticky -> sticky * pretty errir Co-authored-by: Taher Darolywala <tdarolywala@microsoft.com>
* Add keda/dapr version. * Fix.
* Add managedBy property to the containerapps ARM envelope * Add missing prop from previous version * Add managedBy example * Fix ci issues * Allow update of managedBy
…21718)" (Azure#22149) This reverts commit 678bb82.
* Add quotas property to managed environment * lint
* Adding Container App Jobs specs for review * Adding Container App Jobs specs for review * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | address comments * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | fix validations * Adding Container App Jobs specs for review | address comments * Adding Container App Jobs specs for review | address comments * Adding Container App Jobs specs for review | address comments * Adding Container App Jobs specs for review | address comments * Adding Container App Jobs specs for review | address comments * Adding Container App Jobs specs for review | address comments * Adding Container App Jobs specs for review | address comments * updating sub-resource name to jobs from containerAppsJobs * updating sub-resource name to jobs from containerAppsJobs * updating sub-resource name to jobs from containerAppsJobs * updating sub-resource name to jobs from containerAppsJobs * updating sub-resource name to jobs from containerAppsJobs * revert resource management version * revert resource management version * revert resource management version
Co-authored-by: Vincent He <dashe@microsoft.com>
* Fix S360 certificateId not required * Fix example --------- Co-authored-by: Nan Jiang <naji@microsoft.com>
* add properties for secrets from KV * typo * remove unnecessay examples
…#22594) * update start stop spec for jobs * update start stop spec for jobs * update start stop spec for jobs * update start stop spec for jobs * update start stop spec for jobs * update start stop spec for jobs * update start stop spec for jobs * update start stop spec for jobs * update job specs with start, stop, execution endpoints * update job specs with start, stop, execution endpoints * update job specs with start, stop, execution endpoints * update start stop spec for jobs * update start stop spec for jobs * update start stop spec for jobs * update start stop spec for jobs * update start stop spec for jobs * update start stop spec for jobs
* add secret volume type to common definitions * updated common definitions for secrets to be an array of secret item objects --------- Co-authored-by: Stacy Zeng <stacyzeng@microsoft.com>
* remove enum category properties * Rename property to category in available workload profiles * Remove premium from description * Update example
* Add infrastructureResourceGroup propery to managedEnvironments * Updated examples * fix indentation * Update examples ref
* Update description for CORS policy properties * Fix 2022-10-01 PATCH response * fix * fix
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
PLease add the base commit before starting the ARM review |
Please ensure to respond feedbacks from the ARM API reviewer. When you are ready to continue the ARM API review, please remove |
What is the base commit you mentioned? Is this one a0b5838? BTW, all changes in this PR already get ARM reviews in separated PR. Here is our feature branch https://github.com/Azure/azure-rest-api-specs/commits/release-app-Microsoft.App-2022-11-01-preview/specification/app. |
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist (MS Employees Only):
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 the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] 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. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.