Skip to content

Comments

Users/prakgupta/metrics stable version#37945

Merged
Prakriti-nith merged 4 commits intomainfrom
users/prakgupta/metricsStableVersion
Oct 10, 2025
Merged

Users/prakgupta/metrics stable version#37945
Prakriti-nith merged 4 commits intomainfrom
users/prakgupta/metricsStableVersion

Conversation

@Prakriti-nith
Copy link
Member

@Prakriti-nith Prakriti-nith commented Oct 7, 2025

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.

spec_pr_review_workflow_diagram

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.
  • Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
  • Other, please clarify:
    Creating a new stable version from existing preview version 2025-07-07-preview. No change in API spec from base version.

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.
  • A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

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
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.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • 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.
  • For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.

@github-actions
Copy link

github-actions bot commented Oct 7, 2025

Next Steps to Merge

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

Comment generated by summarize-checks workflow run.

@github-actions github-actions bot added brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. ARMReview new-api-version resource-manager RPaaS WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Oct 7, 2025
@github-actions
Copy link

github-actions bot commented Oct 7, 2025

API Change Check

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

Language API Review for Package
Swagger PaloAltoNetworks.Cloudngfw
Go sdk/resourcemanager/paloaltonetworksngfw/armpanngfw
Java com.azure.resourcemanager:azure-resourcemanager-paloaltonetworks-ngfw
JavaScript @azure/arm-paloaltonetworksngfw

@github-actions github-actions bot added BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required NotReadyForARMReview BreakingChange-Python-Sdk and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Oct 7, 2025
@Prakriti-nith Prakriti-nith added PublishToCustomers Acknowledgement the changes will be published to Azure customers. IDCDevDiv Liftr Marketplace-Liftr RPs labels Oct 7, 2025
@mikekistler
Copy link
Member

Breaking changes previously reviewed and approved in #35712

@mikekistler mikekistler added the BreakingChange-Approved-Previously Changes were reviewed and approved in a previous PR label Oct 8, 2025
@github-actions github-actions bot added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required and removed NotReadyForARMReview labels Oct 8, 2025
@nineela nineela added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Oct 9, 2025
@github-actions github-actions bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Oct 9, 2025
@nineela
Copy link
Contributor

nineela commented Oct 9, 2025

The PR has no spec changes and is a new stable version of the earlier released 2025-07-07-preview.

@Prakriti-nith Prakriti-nith enabled auto-merge (squash) October 10, 2025 06:54
@Prakriti-nith Prakriti-nith merged commit dbd27c2 into main Oct 10, 2025
40 of 41 checks passed
@Prakriti-nith Prakriti-nith deleted the users/prakgupta/metricsStableVersion branch October 10, 2025 07:05
pmoana-ms pushed a commit that referenced this pull request Oct 23, 2025
* Add version 2025-07-07-preview as base for releasing a new stable version

* Update API version to 2025-10-08

* Add new tag in README.md

---------

Co-authored-by: Prakriti Gupta <prakgupta@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review BreakingChange-Approved-Previously Changes were reviewed and approved in a previous PR BreakingChange-Python-Sdk BreakingChange-Python-Sdk-Approved BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. IDCDevDiv Liftr Marketplace-Liftr RPs new-api-version PublishToCustomers Acknowledgement the changes will be published to Azure customers. resource-manager RPaaS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants