-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
databricks: switching parameters
to be a proper struct
#7872
databricks: switching parameters
to be a proper struct
#7872
Conversation
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goA PR has been created for you: |
Please add code owner to reviewer. Also please try to pass CI as well. If you think any validation is not your fault please raise it. |
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.
I'm assuming that this is not breaking as the newly defined properties match the complete list of properties supported by the service previously? With that in mind, signing off. If this is breaking ,please expose in a new API version
You don't have permission to trigger SDK Automation. |
…aceCreateWithParameters.json
4e98936
to
97a68f3
Compare
97a68f3
to
592d22b
Compare
@weidongxu-microsoft @KrisBash thanks for reviewing - the tests pass now 👍 |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
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-sdk-for-go - Release
|
azure-sdk-for-js - 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-python - Release
|
* databricks: switching `parameters` to be a proper struct * removing the unused required field * linting * DataBricks: matching the Swagger to the API request/response * Refactor nexamples/WorkspaceCreateParameters.json - > examples/WorkspaceCreateWithParameters.json * prettier * Update 201 body * Update resourceTags * DataBricks: fixing the parameter types
This is a continuation of #6917
From #6917
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.