Skip to content

[WIP] Microsoft.Web, New API 2024 01 01#27055

Closed
Francisco-Gamino wants to merge 6 commits intomainfrom
Francisco-Gamino-web-Microsoft.Web-2024-01-01
Closed

[WIP] Microsoft.Web, New API 2024 01 01#27055
Francisco-Gamino wants to merge 6 commits intomainfrom
Francisco-Gamino-web-Microsoft.Web-2024-01-01

Conversation

@Francisco-Gamino
Copy link
Copy Markdown
Contributor

@Francisco-Gamino Francisco-Gamino commented Dec 13, 2023

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 Description

This PR contains the following changes:

  • Added initial based commit (copied 2023-01-01 API version)
  • Added functionAppConfig definition
  • Added CreateOrUpdateWebApp2.json example (this is a copy of CreateOrUpdateWebApp.json with the new added functionAppConfig section)

PR review workflow diagram

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

diagram

Click here to see the details of Step 1

Breaking changes review (Diagram Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

  • The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
  • You believe there is no need for you to request breaking change approval, for any reason.
    Such claims must be reviewed, and the process is the same.
Click here to see the details of Step 2

ARM API changes review (Diagram Step 2)

  • If this PR is in purview of ARM review then automation will add the ARMReview label.
  • If you want to force ARM review, add the label yourself.
  • Proceed according to the diagram at the top of this comment.
Click here to see the diagram footnotes

Diagram footnotes

[1] ARM review queue (for merge queues, see [2])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])

If you need further help with anything, see Getting help section below.

Purpose of this PR

What's the purpose of this PR? Check all that apply. This is mandatory!

  • New API version. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
  • 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 swagger 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

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
Swagger-Suppression-Process
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.
  • 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.

@rkmanda
Copy link
Copy Markdown
Member

rkmanda commented Dec 13, 2023

/azp run

@openapi-pipeline-app
Copy link
Copy Markdown

openapi-pipeline-app Bot commented Dec 13, 2023

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ Your PR has breaking changes (label: BreakingChangeReviewRequired). See the PR description for help.
  • ❌ The required check named Breaking Change(Cross-Version) has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it. In addition, refer to step 1 in the PR workflow diagram (even if your PR is for data plane, not ARM).

@openapi-pipeline-app
Copy link
Copy Markdown

openapi-pipeline-app Bot commented Dec 13, 2023

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️❌Breaking Change(Cross-Version): 3 Errors, 5 Warnings failed [Detail]
compared swaggers (via Oad v0.10.4)] new version base version
AppServiceEnvironments.json 2024-01-01(fffa0c9) 2023-01-01(main)
AppServicePlans.json 2024-01-01(fffa0c9) 2023-01-01(main)
Certificates.json 2024-01-01(fffa0c9) 2023-01-01(main)
CommonDefinitions.json 2024-01-01(fffa0c9) 2023-01-01(main)
ContainerApps.json 2024-01-01(fffa0c9) 2023-01-01(main)
ContainerAppsRevisions.json 2024-01-01(fffa0c9) 2023-01-01(main)
DeletedWebApps.json 2024-01-01(fffa0c9) 2023-01-01(main)
Diagnostics.json 2024-01-01(fffa0c9) 2023-01-01(main)
Global.json 2024-01-01(fffa0c9) 2023-01-01(main)
KubeEnvironments.json 2024-01-01(fffa0c9) 2023-01-01(main)
Provider.json 2024-01-01(fffa0c9) 2023-01-01(main)
Recommendations.json 2024-01-01(fffa0c9) 2023-01-01(main)
ResourceHealthMetadata.json 2024-01-01(fffa0c9) 2023-01-01(main)
ResourceProvider.json 2024-01-01(fffa0c9) 2023-01-01(main)
StaticSites.json 2024-01-01(fffa0c9) 2023-01-01(main)
WebApps.json 2024-01-01(fffa0c9) 2023-01-01(main)

The following breaking changes are detected by comparison with the latest stable version:

Rule Message
1033 - RemovedProperty The new version is missing a property found in the old version. Was 'provisioningState' renamed or removed?
New: Microsoft.Web/stable/2024-01-01/CommonDefinitions.json#L2269:7
Old: Microsoft.Web/stable/2023-01-01/CommonDefinitions.json#L2554:11
1033 - RemovedProperty The new version is missing a property found in the old version. Was 'privateEndpoint' renamed or removed?
New: Microsoft.Web/stable/2024-01-01/CommonDefinitions.json#L2269:7
Old: Microsoft.Web/stable/2023-01-01/CommonDefinitions.json#L2554:11
1033 - RemovedProperty The new version is missing a property found in the old version. Was 'ipAddresses' renamed or removed?
New: Microsoft.Web/stable/2024-01-01/CommonDefinitions.json#L2269:7
Old: Microsoft.Web/stable/2023-01-01/CommonDefinitions.json#L2554:11
⚠️ 1017 - ReferenceRedirection The '$ref' property points to different models in the old and new versions.
New: Microsoft.Web/stable/2024-01-01/AppServiceEnvironments.json#L1648:13
Old: Microsoft.Web/stable/2023-01-01/AppServiceEnvironments.json#L1648:13
⚠️ 1017 - ReferenceRedirection The '$ref' property points to different models in the old and new versions.
New: Microsoft.Web/stable/2024-01-01/CommonDefinitions.json#L2284:9
Old: Microsoft.Web/stable/2023-01-01/CommonDefinitions.json#L2551:9
⚠️ 1017 - ReferenceRedirection The '$ref' property points to different models in the old and new versions.
New: Microsoft.Web/stable/2024-01-01/StaticSites.json#L3066:13
Old: Microsoft.Web/stable/2023-01-01/StaticSites.json#L3066:13
⚠️ 1017 - ReferenceRedirection The '$ref' property points to different models in the old and new versions.
New: Microsoft.Web/stable/2024-01-01/WebApps.json#L7573:13
Old: Microsoft.Web/stable/2023-01-01/WebApps.json#L7573:13
⚠️ 1017 - ReferenceRedirection The '$ref' property points to different models in the old and new versions.
New: Microsoft.Web/stable/2024-01-01/WebApps.json#L16855:13
Old: Microsoft.Web/stable/2023-01-01/WebApps.json#L16855:13
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️🔄LintDiff inProgress [Detail]
️❌Avocado: 32 Errors, 0 Warnings failed [Detail]

Only 30 items are listed, please refer to log for more details.

Rule Message
UNREFERENCED_JSON_FILE The example JSON file is not referenced from the swagger file.
readme: specification/web/resource-manager/readme.md
json: stable/2024-01-01/examples/CreateOrUpdateWebApp2.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.CertificateRegistration/certificateOrders is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.CertificateRegistration/validateCertificateRegistrationInformation is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/certificates is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/certificates/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/reissue is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/renew is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/resendEmail is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/resendRequestEmails is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/retrieveSiteSeal is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/verifyDomainOwnership is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/retrieveCertificateActions is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/retrieveEmailHistory is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/AppServiceCertificateOrders.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /providers/Microsoft.CertificateRegistration/operations is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/CertificateRegistrationProvider.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/detectors is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/CertificateOrdersDiagnostics.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.CertificateRegistration/certificateOrders/{}/detectors/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.CertificateRegistration/stable/2023-01-01/CertificateOrdersDiagnostics.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /providers/Microsoft.DomainRegistration/operations is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/DomainRegistrationProvider.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.DomainRegistration/checkDomainAvailability is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/Domains.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.DomainRegistration/domains is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/Domains.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.DomainRegistration/generateSsoRequest is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/Domains.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.DomainRegistration/listDomainRecommendations is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/Domains.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.DomainRegistration/domains is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/Domains.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.DomainRegistration/domains/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/Domains.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.DomainRegistration/domains/{}/domainOwnershipIdentifiers is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/Domains.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.DomainRegistration/domains/{}/domainOwnershipIdentifiers/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/Domains.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.DomainRegistration/domains/{}/renew is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/Domains.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.DomainRegistration/topLevelDomains is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/TopLevelDomains.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.DomainRegistration/topLevelDomains/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.
readme: specification/web/resource-manager/readme.md
json: Microsoft.DomainRegistration/stable/2023-01-01/TopLevelDomains.json
️❌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.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️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
Copy link
Copy Markdown

openapi-pipeline-app Bot commented Dec 13, 2023

Swagger Generation Artifacts

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

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

️❌SDK Breaking Change Tracking failed [Detail]

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-track2 warning [Detail]

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

️⚠️ azure-sdk-for-java warning [Detail]

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 inProgress [Detail]
️⚠️ 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
Copy link
Copy Markdown

openapi-pipeline-app Bot commented Dec 13, 2023

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 3 pipeline(s).

@openapi-workflow-bot
Copy link
Copy Markdown

Hi @Francisco-Gamino! For review efficiency consideration, when creating a new API version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version.
For more details refer to the wiki.

@AzureRestAPISpecReview AzureRestAPISpecReview added the BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required label Dec 16, 2023
@Francisco-Gamino
Copy link
Copy Markdown
Contributor Author

This PR is replaced by #27358

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants