-
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
[Datafactory] Add folders to Pipeline and Dataset #3636
Conversation
Adding folders to pipeline definition
Adding folders to Dataset definition
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaThe initial PR has been merged into your service PR: |
Can one of the admins verify this patch? |
@@ -37,6 +37,16 @@ | |||
"items": { | |||
"type": "object" | |||
} | |||
}, | |||
"folder": { | |||
"description": "The folder that this Dataset is in.", |
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.
If this property is omitted, is there a default folder that is used? If so, it may be worth mentioning.
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.
All the entities will appear at the root level unless a folder is specified. If that is worth mentioning then i can add that in
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.
Your call :)
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.
Changed!
"type": "object", | ||
"properties": { | ||
"name": { | ||
"description": "The name of the folder that this Dataset is in.", |
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.
Same here
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
This change should ideally go in a new api-version. In strongly typed SDKs, the property will be ignored. And the object which is returned from the GET is used for PUT, it can unintentionally override the state of the resource on the server and now the pipeline will be at root level? |
Folders is already being used, especially in the webapp/UI to organize the resources. Currently customers who have pipelines/datasets with folders and try to deploy them with the SDK loose their folder information. I don't think it needs to go into a new api version as it is not a introducing a new behavior but rather is helping customers get unblocked from their current experience |
@ravbhatnagar @marstr any pending comments/updates? |
From my side, I'm waiting for @ravbhatnagar to remove the WaitForARMFeedback label to confirm whether or not he approves of adding new parameters inside of an API version. His concern about slicing should be taken seriously. :) |
I'm going to be OOF all next week, so I'm going to have this PR reassigned. |
@arsunda When you say "already being used", do you mean that on the service side they are already implemented in the current api-version? Please confirm. |
Got confirmation from service team that this has existed on the service side. The change is only adding it to swagger now. Signing off from ARM side. |
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
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-version
in the path should match theapi-version
in the spec).Quality of Swagger
Related task: https://msdata.visualstudio.com/Azure%20Data%20Factory/_workitems/edit/277770