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

Change connection-string to be object and support making severname, d… #2834

Merged
merged 2 commits into from
Apr 20, 2018

Conversation

zhanyu2014
Copy link
Contributor

@zhanyu2014 zhanyu2014 commented Apr 8, 2018

…atabasename visible to customers

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

@msftclas
Copy link

msftclas commented Apr 8, 2018

CLA assistant check
All CLA requirements met.

@AutorestCI
Copy link

AutorestCI commented Apr 8, 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 Apr 8, 2018

Automation for azure-libraries-for-java

The initial PR has been merged into your service PR:
AutorestCI/azure-libraries-for-java#18

@AutorestCI
Copy link

AutorestCI commented Apr 8, 2018

Automation for azure-sdk-for-go

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-go#1640

@AutorestCI
Copy link

AutorestCI commented Apr 8, 2018

Automation for azure-sdk-for-node

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

Copy link
Member

@marstr marstr left a comment

Choose a reason for hiding this comment

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

The descriptions should really be updated to mention that there is a non-trivial string type.

@@ -104,7 +104,7 @@
"properties": {
"connectionString": {
"description": "The connection string.",
"$ref": "../datafactory.json#/definitions/SecretBase"
"type": "object"
Copy link
Member

Choose a reason for hiding this comment

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

I see SecretBase was an object with a property type. Does that continue to be true here? Reading the description without the context of this PR, I would be surprised if this was anything but a string.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Before the connectionString was defined as SecretBase, and customers can only give value as "SecureString" or "AKV" (Two data contract used in ADF) for this field. Now we want to support customer to provide value with string directly while the existed "SecureString" and "AKV" can still work, so we change its type to be object.

"type": "object"
},
"encryptedCredential": {
"description": "The encrypted credential used for authentication. Credentials are encrypted using the integration runtime credential manager. Type: string (or Expression with resultType string).",
Copy link
Member

Choose a reason for hiding this comment

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

Ah, I'm presuming that this is the answer to my question above. It would be worth adding that to the description, if it's the case.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Description is updated.

@marstr
Copy link
Member

marstr commented Apr 9, 2018

Ah, another thing that I should point out @zhanyu2014 is that it says your CLA hasn't been signed. I assume you're a Microsoft employee, so you should go to http://opensource and join the appropriate organizations.

@Azure Azure deleted a comment from AutorestCI Apr 10, 2018
@Azure Azure deleted a comment from AutorestCI Apr 10, 2018
@Azure Azure deleted a comment from AutorestCI Apr 10, 2018
@Azure Azure deleted a comment from AutorestCI Apr 10, 2018
@marstr marstr added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 10, 2018
@marstr
Copy link
Member

marstr commented Apr 10, 2018

Adding the ARM review label before I forget.

@jhendrixMSFT
Copy link
Member

@AutorestCI regenerate azure-sdk-for-go

@azuresdkciprbot
Copy link

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/datafactory/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 1
After the PR: Warning(s): 0 Error(s): 1

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

1 similar comment
@azuresdkciprbot
Copy link

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/datafactory/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 1
After the PR: Warning(s): 0 Error(s): 1

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@marstr
Copy link
Member

marstr commented Apr 13, 2018

I'd like to remind you @zhanyu2014 that our License CLA bot still says that you are not appropriately documented as a Microsoft Employee. I cannot merge this PR until your CLA is recognized.

@marstr
Copy link
Member

marstr commented Apr 16, 2018

Please acknowledge, @zhanyu2014. If I see no response, I'll have to close this PR as inactive.

@zhanyu2014
Copy link
Contributor Author

The related SLA has been validated and passed, related comments in change has been resolved, please help continue to finish this review and merge it. @marstr, @jianghaolu.

@marstr
Copy link
Member

marstr commented Apr 17, 2018

The only thing remaining now is @ravbhatnagar or another ARM representative to sign off. Thanks for signing the CLA, @zhanyu2014.

@ravbhatnagar ravbhatnagar added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Apr 19, 2018
@marstr
Copy link
Member

marstr commented Apr 19, 2018

Ready for me to merge, @zhanyu2014?

@zhanyu2014
Copy link
Contributor Author

@marstr, please help us finish the code merge.

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants