Skip to content

Conversation

@boxiao-o
Copy link
Contributor

@boxiao-o boxiao-o commented Nov 1, 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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Nov 1, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Nov 1, 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 Nov 1, 2018

Automation for azure-sdk-for-js

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-js#411

@AutorestCI
Copy link

AutorestCI commented Nov 1, 2018

Automation for azure-sdk-for-java

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

@AutorestCI
Copy link

AutorestCI commented Nov 1, 2018

Automation for azure-sdk-for-go

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

@AutorestCI
Copy link

AutorestCI commented Nov 1, 2018

Automation for azure-sdk-for-node

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

Copy link
Member

@jhendrixMSFT jhendrixMSFT left a 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?

@boxiao-o
Copy link
Contributor Author

boxiao-o commented Nov 2, 2018

@jhendrixMSFT May I know which file to update? If LinkedServices_Create.json in examples folder, those fields I added is optional and will only be used in some special cases, so may not need to be added there.

…AzureKeyVaultSecretReference, same with connection string.
@jhendrixMSFT
Copy link
Member

@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": {
Copy link
Contributor

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?

Copy link
Contributor Author

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": {
Copy link
Contributor

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

Copy link
Contributor Author

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.

@boxiao-o
Copy link
Contributor Author

boxiao-o commented Nov 5, 2018

@jhendrixMSFT Seems based on our convention, we usually do not update example here, but I will update the examples in sdk JsonSamples

@jhendrixMSFT
Copy link
Member

@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.

@jhendrixMSFT jhendrixMSFT merged commit 3869689 into Azure:master Nov 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants