Skip to content

Add platformReleaseChannel property to Webapp Site model#40557

Closed
sarsharma wants to merge 4 commits intoAzure:mainfrom
sarsharma:add-platformReleaseChannel-to-site-model
Closed

Add platformReleaseChannel property to Webapp Site model#40557
sarsharma wants to merge 4 commits intoAzure:mainfrom
sarsharma:add-platformReleaseChannel-to-site-model

Conversation

@sarsharma
Copy link
Copy Markdown
Member

@sarsharma sarsharma commented Feb 19, 2026

Add platformReleaseChannel property to Site model

Description

This PR adds the platformReleaseChannel property to the Site resource model
The Azure App Service platform supports a release channel configuration (Latest, Standard, or Extended) that controls the order in which platform updates are applied to web apps:

Related PRs

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 19, 2026

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
    This PR is not ready for ARM review (label: NotReadyForARMReview). This PR will not be reviewed by ARM until relevant problems are fixed. Consult the rest of this Next Steps to Merge comment for details.
    Once the blocking problems are addressed, add to the PR a comment with contents /azp run. Automation will re-evaluate this PR and if everything looks good, it will add WaitForARMFeedback label which will put this PR on the ARM review queue.
    For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  • ❌ This PR is NotReadyForARMReview because it has the VersioningReviewRequired label.
  • ❌ This PR has at least one change violating Azure versioning policy (label: VersioningReviewRequired).
    To unblock this PR, either a) introduce a new API version with these changes instead of modifying an existing API version, or b) follow the process at aka.ms/brch.
  • ❌ The required check named Swagger BreakingChange has failed. To unblock this PR, follow the process at aka.ms/brch.


Comment generated by summarize-checks workflow run.

@sarsharma sarsharma marked this pull request as draft February 19, 2026 20:25
@sarsharma sarsharma closed this Feb 19, 2026
@sarsharma sarsharma force-pushed the add-platformReleaseChannel-to-site-model branch from 11b837a to ca527fa Compare February 19, 2026 20:27
@sarsharma sarsharma changed the title Add platformReleaseChannel property to Site model (2024-11-01) Add platformReleaseChannel property to Webapp Site model Feb 19, 2026
@sarsharma sarsharma reopened this Feb 19, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 19, 2026

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger Microsoft.Web-AppService
JavaScript @azure/arm-appservice
Java com.azure.resourcemanager:azure-resourcemanager-appservice-generated
TypeSpec Microsoft.Web
Go sdk/resourcemanager/appservice/armappservice
Java com.azure.resourcemanager:azure-resourcemanager-appservice

@sarsharma sarsharma marked this pull request as ready for review February 20, 2026 05:22
@github-actions github-actions Bot added ARMReview WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Feb 20, 2026
@sarsharma sarsharma force-pushed the add-platformReleaseChannel-to-site-model branch from 104fea0 to 2a780f6 Compare February 20, 2026 13:20
@github-actions github-actions Bot added TypeSpec Authored with TypeSpec and removed ARMReview labels Feb 20, 2026
@github-actions github-actions Bot added the VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required label Feb 20, 2026
@sarsharma sarsharma marked this pull request as ready for review February 20, 2026 14:27
@github-actions github-actions Bot added ARMReview NotReadyForARMReview and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Feb 20, 2026
@microsoft-github-policy-service microsoft-github-policy-service Bot added no-recent-activity There has been no recent activity on this issue. and removed no-recent-activity There has been no recent activity on this issue. labels Mar 9, 2026
@microsoft-github-policy-service microsoft-github-policy-service Bot added no-recent-activity There has been no recent activity on this issue. and removed no-recent-activity There has been no recent activity on this issue. labels Mar 23, 2026
@sarsharma sarsharma marked this pull request as draft March 26, 2026 07:09
@sarsharma sarsharma marked this pull request as ready for review April 17, 2026 17:30
@sarsharma sarsharma requested a review from danielw5 as a code owner April 17, 2026 17:30
@sarsharma sarsharma closed this Apr 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMReview NotReadyForARMReview resource-manager SuppressionReviewRequired TypeSpec Authored with TypeSpec VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required Web Apps

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants