SDK generation and regeneration completed for NetApp TypeSpec project (2025-09-01 stable) #38813
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SDK configuration pull request
Purpose of this PR
This PR tracks SDK generation and regeneration for the NetApp TypeSpec project at
/specification/netapp/resource-manager/Microsoft.NetApp/NetAppfor API version 2025-09-01 (stable release).Status: SDK regeneration completed per service team request. 4 of 5 languages succeeded.
SDK Regeneration Results (Latest)
All SDKs were regenerated on 2025-11-14 per service team request.
✅ Successfully Regenerated (4/5)
azure-resourcemanager-netapp(Build 5574883) - Updatedazure-mgmt-netapp(Build 5574882) - New PR@azure/arm-netapp(Build 5574881) - Updatedsdk/resourcemanager/netapp/armnetapp(Build 5574879) - New PR❌ Failed Regeneration (1/5)
Release Details
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:
tspconfig.yamltemplates: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.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.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.