-
Notifications
You must be signed in to change notification settings - Fork 5.6k
[DataFactory]Add sensitive fields extracted from connection string in swagger for AKV reference #4375
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 sensitive fields extracted from connection string in swagger for AKV reference #4375
Conversation
|
Can one of the admins verify this patch? |
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: |
Automation for azure-sdk-for-jsA 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: |
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: |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
jhendrixMSFT
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.
Can you please update the affected examples with the new fields?
|
@jhendrixMSFT May I know which file to update? If |
…AzureKeyVaultSecretReference, same with connection string.
|
@boxiao-o If these fields are optional then perhaps it makes more sense to add a new example that uses them? |
| "description": "An ODBC connection string. Type: string, SecureString or AzureKeyVaultSecretReference.", | ||
| "type": "object" | ||
| }, | ||
| "pwd": { |
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.
Why is this one named pwd while others password?
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 property name needs to be same with the name in connection string. In this Netezza linked service case, a typical connection string is Server=<server>;Port=<port>;Database=<database>;UID=<user name>;PWD=<password>.
| "description": "An ODBC connection string. Type: string, SecureString or AzureKeyVaultSecretReference.", | ||
| "type": "object" | ||
| }, | ||
| "credString": { |
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.
Here too, please use full words in names
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. This field will be back-filled into connection string, so the name should be the same.
|
@jhendrixMSFT Seems based on our convention, we usually do not update example here, but I will update the examples in sdk JsonSamples |
|
@boxiao-o I'm not sure what you mean by "based on our convention". The example files are used to generate documentation so if you want these fields doc'ed you should add an example for them. |
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