-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove enum from catalogPricingTier #5278
Conversation
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-nodeA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Can one of the admins verify this patch? |
Automation for azure-sdk-for-jsA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
What's the reason for this change? How can customers discover what string to provide? |
This is actually a increasing list which comes from Azure SQL database. If we make it enum here, we need to update the list from time to time, so we decided to just change it to string and document it with a link from Azure SQL Database site. The current enum list is actually incorrect and out of date. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay and thanks for the explanation.
You can keep the changes for the preview spec but you cannot change the stable spec. You will have to include this breaking change in the next API version update.
"name": "IntegrationRuntimeSsisCatalogPricingTier", | ||
"modelAsString": true | ||
} | ||
"type": "string" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not allowed though. This is a stable API version so no breaking changes can be introduced.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jianghaolu I revoked the changes in stable API version.
REST Spec PR 'Azure/azure-rest-api-specs#5278' REST Spec PR Author 'zhangyd2015' REST Spec PR Last commit
Automation for azure-sdk-for-netA PR has been created for you: |
@jianghaolu Could you please merge this PR if there is no further comments? Thanks. |
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.