Updated Swagger as per latest changes.#8427
Conversation
Added the missing 'description' field in CreatedBy element
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-python - Release
|
azure-sdk-for-go - Release
|
azure-sdk-for-java - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-net - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-js - Release
|
|
WaitForARMFeedback |
added readonly attribute to properties
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Can you please update with below changes as discussed offline.
|
Fixed all the below review comments. 1. New property 'properties.parameters.enableFedRampCertified' 2. Returning 'properties.CreatedDateTime' 3. VNet peering in the operation list 4. AML workspace id in the example should be a resource uri 5. Sku name value should be allowed value (in the example) 6. Revert changes to remove properties 7. Update examples as well.
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@yungezz can you confirm when we can merge this PR? |
Fixed model validation errors.
| "description": "Specifies the date and time when the workspace is created.", | ||
| "$ref": "#/definitions/CreatedDateTime" | ||
| }, | ||
| "workspaceId": { |
There was a problem hiding this comment.
adding properties to existing version is breaking change. need to do it in new version
There was a problem hiding this comment.
@yungezz We're going to backfill all existing databricks workspaces with these 2 properties. Any new workspaces created with this api-version will get these 2 properties by default. And all existing workspaces, we're going to backfill them next week. So this shouldn't technically remain as a breaking change after the backfilling is done. Also, since the backfill process is scheduled for next week, we request you to put a "DoNotMerge" label until we complete the process.
There was a problem hiding this comment.
HI @amoghnatu, thanks for sharing this. Adding new properties in response will break the GET-PUT pipeline, here's guideline of breaking change https://github.com/Azure/adx-documentation-pr/wiki/Breaking-changes-guidelines#new-property-added-to-response
There was a problem hiding this comment.
@yungezz Thanks for mentioning this. However, in our case, these 2 new properties are readonly and the customer will not be able to set them. Also, these are not available in the template so user cannot set them to provide as input. I have updated the spec to include readonly=true for these 2 properties. Kindly check.
|
since there're new properties added after ARM signoff. need ARM review again. Wait for ARM review. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi @amoghnatu, Looks there is some change for package-lock.json file in your PR which is not supposed in swagger PR. can you remove this file change in this PR? Thanks |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@akning-ms Thanks for pointing it out. I have removed the file. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
signing off from ARM side. |
|
hi @amoghnatu, could you pls fix CI failure, then the PR ok to merge. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-cli-extensions - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
|
hi @amoghnatu could you pls fix CI? |
|
ping @amoghnatu |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.