Add 2025-11-01-preview version to Microsoft.Subscription#37722
Add 2025-11-01-preview version to Microsoft.Subscription#37722ComradeCow merged 4 commits intomainfrom
2025-11-01-preview version to Microsoft.Subscription#37722Conversation
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. |
|
Waiting to merge this until #37575 is merged. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
867dc16 to
d6ac262
Compare
|
Breaking changes previously reviewed and approved in #29912. |
| "description": "Subscription Changed Target Directory response properties." | ||
| }, | ||
| "systemData": { | ||
| "$ref": "../../../../../common-types/resource-management/v5/types.json#/definitions/systemData", |
There was a problem hiding this comment.
Updated all the shared type references to v6.
| "format": "date-time", | ||
| "x-nullable": true | ||
| }, | ||
| "sourceOwnerEmail": { |
There was a problem hiding this comment.
Is there a pattern for email? I couldn't find examples in the repository.
There was a problem hiding this comment.
me neither, low pri/ nice to have.
| "description": "The id of the subscription being transferred.", | ||
| "readOnly": true, | ||
| "type": "string", | ||
| "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$" |
There was a problem hiding this comment.
I'm not either, and I'd love to hear if there is. Doing a search through the repo there's a 1001 different ways guids get specified. I originally had "format": "uuid" but was told not to use that because of how it gets interpreted for some SDKs to use a guid type rather than string? Not sure what the best pattern is.
| "enum": [ | ||
| "Initialized", | ||
| "InProgress", | ||
| "Completed" |
There was a problem hiding this comment.
pretty self explanatory, but might be helpful to add description to add more context/info for doc purpose. #Resolved
There was a problem hiding this comment.
Added the values in x-ms-enum.
|
please take a look at the avocado failure as well. |
d6ac262 to
a0ee0b6
Compare
|
The Avocado current errors should be resolved with #37575 as that resolves the MULTIPLE_API_ERROR code. There will be errors remaining for the deprecated apis that we will need the |
|
@ComradeCow are you handling the avocado error? I still see it. |
Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec.
Updated the API version from preview/2024-08-01-preview to preview/2025-11-01-preview.
a0ee0b6 to
9a21c61
Compare
|
#37575 has now been merged which cleans up the Avocado errors. |
|
(poking to keep this pr from going stale) |
|
(poking to keep this pr from going stale) |
|
(poking to keep this pr from going stale) |
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection 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!
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:
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 ApiViewcomment 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
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.