-
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
[Datafactory] Add Support for Managed Private Endpoints and Virtual Networks Resources #10191
[Datafactory] Add Support for Managed Private Endpoints and Virtual Networks Resources #10191
Conversation
[Staging] Swagger Validation Report
️✔️ |
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-js - Release
|
azure-sdk-for-java - Release
|
azure-sdk-for-python - Release
|
azure-sdk-for-python-track2 - 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-net - Release
|
Trenton Generation - 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
|
Can one of the admins verify this patch? |
Azure CLI Extension Generation - 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). |
Hi @qianwens my changes are ready for review. Please take a look, thanks #Resolved |
As per https://github.com/microsoft/api-guidelines/blob/vNext/azure/Guidelines.md additions of new endpoints fall under the umbrella of evolutionary changes and therefore require an API version bump. #Resolved |
Hi @majastrz I am not adding a new endpoint. I am adding CRUD APIs for two new subresources for Azure Data Factory. The resource names are managed Private Endpoint and managed Virtual Network. #Resolved |
}, | ||
"304": { | ||
"description": "Not modified." | ||
}, |
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.
GETs should only return 200 OK or an error. #Resolved
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.
Fixed, thanks #Resolved
}, | ||
"304": { | ||
"description": "Not modified." | ||
}, |
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.
GETs should only return 200 OK or an error. #Resolved
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.
Fixed, thanks #Resolved
"ifMatch": null, | ||
"managedPrivateEndpoint": { | ||
"properties": { | ||
"description": "A managed private endpoint", |
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.
description [](start = 9, length = 11)
Why is description not being returned in PUT response? #Resolved
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.
Removed the description. It is not supported. Thanks for catching the issue #Resolved
"ifMatch": null, | ||
"managedVirtualNetwork": { | ||
"properties": { | ||
"description": "A managed Virtual network" |
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.
description [](start = 9, length = 11)
Same question here #Resolved
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.
Removed the description as it is currently not supported. #Resolved
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.
thanks #Resolved
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Signed off from ARM side.
@qianwens can please help merge this PR? |
…etworks Resources (Azure#10191) * initial changes * fix example file name reference * fix error * more fixes * fix typo * add nextlink to PE API * update example for PE List API * fix style issues * address review comments * correct example * fix prettier issues
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
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 PR review process.