Conversation
…review cycle. This allows reviewers to easily diff subsequent changes against the previous spec. It is based on release-Microsoft.FileShares-2024-01-01-preview In https://github.com/Azure/azure-rest-api-specs-pr
Based on private API version: 2024-01-01-preview
…ctor MediaTier, Redundancy, Protocol, and ShareRootSquash to use union types
…tSquash to specify they are enums
… to improve outcome of Az PowerShell generation
Next Steps to MergeNext steps that must be taken to merge this PR:
|
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
…/2025-06-01-preview
* Revert changes to snapshot proxy resource * Update readme.md * Update fileshares.tsp * Add 200 response to snapshots PATCH * Update readme.md * Update readme.md * Update readme.md * Update readme.md * Update readme.md * Update readme.md * Add 200 response example for file share snapshots * Update FileShareSnapshot_Update_MaximumSet_Gen.json
* Revert changes to snapshot proxy resource * Update readme.md * Update fileshares.tsp * Add 200 response to snapshots PATCH * Update readme.md * Update readme.md * Update readme.md * Update readme.md * Update readme.md * Update readme.md * Add 200 response example for file share snapshots * Update FileShareSnapshot_Update_MaximumSet_Gen.json * Update readme.md
…/2025-06-01-preview
|
/azp run |
|
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
|
/azp run |
|
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
…/2025-06-01-preview
|
/azp run |
|
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
|
This Service was in Private Preview for long time, and had taken exception in 2023 for Private Preview API Version. They are extending the exception for Public Preview as well. |
|
nit - I would suggest including a |
…/2025-06-01-preview
* Add sdk related files to resolve CI * PrivateEndpointID Resource correction in examples * TspConfig yaml changes * prettier * commands npm ci npx tsp format specification\fileshares\FileShares.Management\*.tsp npx tsv specification\fileshares\FileShares.Management npx tsp compile specification\fileshares\FileShares.Management\main.tsp * Prettier command npx prettier --write "specification/fileshares/resource-manager/Microsoft.FileShares/preview/2025-06-01-preview/**/*.json" * revert examples * sdk generation errors * Prettier check on Swagger examples npx prettier --write specification/fileshares/FileShares.Management/examples/2025-06-01-preview/FileShares_CreateOrUpdate_MaximumSet_Gen.json npx prettier --write specification/fileshares/FileShares.Management/examples/2025-06-01-preview/FileShares_Get_MaximumSet_Gen.json npx prettier --write specification/fileshares/FileShares.Management/examples/2025-06-01-preview/FileShares_ListByParent_MaximumSet_Gen.json npx prettier --write specification/fileshares/FileShares.Management/examples/2025-06-01-preview/FileShares_Update_MaximumSet_Gen.json npx prettier --write specification/fileshares/resource-manager/Microsoft.FileShares/preview/2025-06-01-preview/examples/FileShares_CreateOrUpdate_MaximumSet_Gen.json npx prettier --write specification/fileshares/resource-manager/Microsoft.FileShares/preview/2025-06-01-preview/examples/FileShares_Get_MaximumSet_Gen.json npx prettier --write specification/fileshares/resource-manager/Microsoft.FileShares/preview/2025-06-01-preview/examples/FileShares_ListByParent_MaximumSet_Gen.json npx prettier --write specification/fileshares/resource-manager/Microsoft.FileShares/preview/2025-06-01-preview/examples/FileShares_Update_MaximumSet_Gen.json * Update client.tsp * Update client.tsp * Update readme.md * Add examples * Fix examples * revert * Update readme.python.md * update
…/2025-06-01-preview
resolved |
|
Hi @ravimeda , Is this something you can take a look at? Thanks, |
|
Discussed with Ankush to validate the suppressions. Refer to guidelines |
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.