Skip to content
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

Merged
merged 4 commits into from
Aug 28, 2018
Merged

[Datafactory] Add folders to Pipeline and Dataset #3636

merged 4 commits into from
Aug 28, 2018

Conversation

arsunda
Copy link
Contributor

@arsunda arsunda commented Aug 14, 2018

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

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

Related task: https://msdata.visualstudio.com/Azure%20Data%20Factory/_workitems/edit/277770

Adding folders to pipeline definition
Adding folders to Dataset definition
@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#2293

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-java

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-java#2136

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@azuresdkci azuresdkci requested a review from marstr August 14, 2018 17:21
@marstr marstr added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Aug 14, 2018
@marstr marstr requested a review from ravbhatnagar August 14, 2018 17:39
@@ -37,6 +37,16 @@
"items": {
"type": "object"
}
},
"folder": {
"description": "The folder that this Dataset is in.",
Copy link
Member

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.

Copy link
Contributor Author

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your call :)

Copy link
Contributor Author

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.",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-node

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-node#3449

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#2566

@ravbhatnagar
Copy link
Contributor

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?

@arsunda
Copy link
Contributor Author

arsunda commented Aug 15, 2018

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

@arsunda
Copy link
Contributor Author

arsunda commented Aug 17, 2018

@ravbhatnagar @marstr any pending comments/updates?

@marstr
Copy link
Member

marstr commented Aug 17, 2018

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. :)

@marstr
Copy link
Member

marstr commented Aug 24, 2018

I'm going to be OOF all next week, so I'm going to have this PR reassigned.

@marstr marstr removed their assignment Aug 25, 2018
@ravbhatnagar
Copy link
Contributor

@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.
@SDK folks - If the answer to this question is YES, I leave to you folks to decide. It is technically still a breaking change. But its bring SDK behavior at par with service.

@ravbhatnagar
Copy link
Contributor

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.

@ravbhatnagar ravbhatnagar added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Aug 27, 2018
@ravbhatnagar ravbhatnagar removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Aug 27, 2018
Copy link
Member

@lmazuel lmazuel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review Reassign
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants