[AKS] remove "KeyVaultSecretRef" and rename to "ManagedClusterServicePrincipalProfile"#3488
Conversation
…PrincipalProfile"
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
dsgouda
left a comment
There was a problem hiding this comment.
Looks good for the most part, please address the comments.
| ] | ||
| }, | ||
| "KeyVaultSecretRef": { | ||
| "properties": { |
There was a problem hiding this comment.
A. Please note that this could be a breaking change in the SDKs generated
B. Please check if you need to update any of the examples
There was a problem hiding this comment.
@dsgouda I did check the examples, but we weren't using keyVaultSecretRef anywhere so this change still passes oav validate-example.
I did note that this is a breaking change in the PR message. Should I mention it elsewhere? Change to package-version: 5.0.0?
There was a problem hiding this comment.
As long as it is ackowledged, shouldn't be a blocker
…3488) * Making User Details and Offer details required fields * Removing the all-api-versions tag as it is abandoned
This was mistakenly copied from
ContainerServiceServicePrincipalProfileand was never supported by AKS.Since this swagger is built along with the ACS API, this requires renaming the class so their definitions can differ. This may be a breaking change for generated SDKs.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger