Release web 2024 04 01

[naveedaz]

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

• New resource provider.
• New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
• Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
• Update existing version to fix OpenAPI spec quality issues in S360.
• Other, please clarify:
  • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

• I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• I have reviewed following Resource Provider guidelines, including
  ARM resource provider contract and
  REST guidelines (estimated time: 4 hours).
  I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

Details

Setting up new API version '2024-04-01' using guidance at: https://eng.ms/docs/products/azure-developer-experience/design/api-specs/api-specs?tabs=openapi

specification/web/resource-manager has 3 different RPs. This PR adds the new API version to all 3.

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

• First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

[openapi-pipeline-app]

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]

There are no breaking changes.

Compared specs (v0.10.8)	new version	base version
AppServiceCertificateOrders.json	2024-04-01(660b3fe)	2023-12-01(main)
CertificateOrdersDiagnostics.json	2024-04-01(660b3fe)	2023-12-01(main)
CertificateRegistrationProvider.json	2024-04-01(660b3fe)	2023-12-01(main)
DomainRegistrationProvider.json	2024-04-01(660b3fe)	2023-12-01(main)
Domains.json	2024-04-01(660b3fe)	2023-12-01(main)
TopLevelDomains.json	2024-04-01(660b3fe)	2023-12-01(main)
AppServiceEnvironments.json	2024-04-01(660b3fe)	2023-12-01(main)
AppServicePlans.json	2024-04-01(660b3fe)	2023-12-01(main)
Certificates.json	2024-04-01(660b3fe)	2023-12-01(main)
CommonDefinitions.json	2024-04-01(660b3fe)	2023-12-01(main)
ContainerApps.json	2024-04-01(660b3fe)	2023-12-01(main)
ContainerAppsRevisions.json	2024-04-01(660b3fe)	2023-12-01(main)
DeletedWebApps.json	2024-04-01(660b3fe)	2023-12-01(main)
Diagnostics.json	2024-04-01(660b3fe)	2023-12-01(main)
Global.json	2024-04-01(660b3fe)	2023-12-01(main)
KubeEnvironments.json	2024-04-01(660b3fe)	2023-12-01(main)
Provider.json	2024-04-01(660b3fe)	2023-12-01(main)
Recommendations.json	2024-04-01(660b3fe)	2023-12-01(main)
ResourceHealthMetadata.json	2024-04-01(660b3fe)	2023-12-01(main)
ResourceProvider.json	2024-04-01(660b3fe)	2023-12-01(main)
StaticSites.json	2024-04-01(660b3fe)	2023-12-01(main)
WebApps.json	2024-04-01(660b3fe)	2023-12-01(main)

️🔄LintDiff inProgress [Detail]

️️✔️Avocado succeeded [Detail] [Expand]

Validation passes for Avocado.

️❌SwaggerAPIView: 0 Errors, 0 Warnings failed [Detail]

️️✔️TypeSpecAPIView succeeded [Detail] [Expand]

️️✔️ModelValidation succeeded [Detail] [Expand]

Validation passes for ModelValidation.

️️✔️SemanticValidation succeeded [Detail] [Expand]

Validation passes for SemanticValidation.

️️✔️SpellCheck succeeded [Detail] [Expand]

Validation passes for SpellCheck.

️️✔️PR Summary succeeded [Detail] [Expand]

Validation passes for Summary.

️️✔️Automated merging requirements met succeeded [Detail] [Expand]

_{Posted by Swagger Pipeline | How to fix these errors?}

[openapi-pipeline-app]

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]

Only 0 items are rendered, please refer to log for more details.

️❌ azure-sdk-for-net-track2 failed [Detail]

Only 0 items are rendered, please refer to log for more details.

️🔄 azure-sdk-for-python inProgress [Detail]

️️✔️ azure-sdk-for-java succeeded [Detail] [Expand]

Only 0 items are rendered, please refer to log for more details.

️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]

Only 0 items are rendered, please refer to log for more details.

️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]

Only 0 items are rendered, please refer to log for more details.

️❌ azure-resource-manager-schemas failed [Detail]

Only 0 items are rendered, please refer to log for more details.

️⚠️ azure-powershell warning [Detail]

Only 0 items are rendered, please refer to log for more details.

_{Posted by Swagger Pipeline | How to fix these errors?}

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/appservice/armappservice	https://apiview.dev/Assemblies/Review/c727c406be7543caa08a79ce56dda352?revisionId=5e063c6b64a447c3add5d9cbcaa186db
Java	azure-resourcemanager-appservice-generated	https://apiview.dev/Assemblies/Review/a2b80e4fbd144844bca0c504ef8c3337?revisionId=e71f83c2602a44e784b2cca611ec0cf2
JavaScript	@azure/arm-appservice	https://apiview.dev/Assemblies/Review/98dbdc8147d7472b9bdff567a8b291bc?revisionId=32bbe7107f40429ea758d0b238c393b3

[naveedaz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 4 pipeline(s).

[naveedaz]

@msyyc, @tadelesh , @jsntcy, @qiaozha ,
This PR is simply to get a new release branch started with a new API version started. The PR was generated by using the copy-apiversion.ps1 script per the guidelines here:
https://eng.ms/docs/products/azure-developer-experience/design/api-specs/api-specs?tabs=openapi.

Can we please get this reviewed/approved, so developers in our team can start adding PRs with actual changes to the release branch?

[mentat9]

Note to any future reviewers. This PR was created by a script in 3 sections. Files were added with base commits at iteration 1, (Microsoft.Web), iteration 4 (Microsoft.DomaintRegistration), and iteration 7 (Microsoft.CertificateRegistration). Subsequent iterations through iteration 14 are only whitespace changes. ARM signoff occurred at iteration 14.

[naveedaz]

azp /run

[naveedaz]

/pr RequestMerge