-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Add two missing operation API-s into swagger for integration runtime #3662
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
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: |
|
Can one of the admins verify this patch? |
Automation for azure-sdk-for-nodeThe 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-goThe initial PR has been merged into your service PR: |
|
Thanks @zhangyd2015 - there are a number of model validation errors in the examples (both new and old) - could you please take a look? Thanks! |
|
@annatisch Fixed model validation errors in new examples. |
annatisch
left a comment
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.
LGTM - just a few tiny grammar errors in the descriptions.
| "type": "string" | ||
| }, | ||
| "dataFactoryLocation": { | ||
| "description": "The location of the data factory for which the linked integration runtime belong to.", |
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.
"The location of the data factory that the linked integration runtime belongs to."
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.
Done. Thanks.
| "type": "string" | ||
| }, | ||
| "dataFactoryName": { | ||
| "description": "The name of the data factory for which the linked integration runtime belong to.", |
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.
"The name of the data factory that the linked integration runtime belongs to."
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.
Done. Thanks.
| "type": "string" | ||
| }, | ||
| "subscriptionId": { | ||
| "description": "The subscription ID for which the linked integration runtime belong to.", |
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.
"The ID of the subscription that the linked integration runtime belongs to."
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.
Done. Thanks.
|
Thanks @zhangyd2015 - are these new APIs that should be reviewed by ARM? Or are they already live in the service? |
|
Thanks @annatisch. These APIs are already live in the service, they are used by our internal services, per to ARM compliance, they should be put into swagger. I don't think ARM team need review the two APIs. |
Added two missing operation API-s into swagger to make ARM happy.
Microsoft.DataFactory/factories/integrationRuntimes/linkedIntegrationRuntime/action
Microsoft.DataFactory/factories/integrationruntimes/nodes/read
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger