Skip to content

Conversation

@natinimni
Copy link
Contributor

@natinimni natinimni commented Jul 9, 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

@AutorestCI
Copy link

AutorestCI commented Jul 9, 2018

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Jul 9, 2018

Automation for azure-sdk-for-go

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

@AutorestCI
Copy link

AutorestCI commented Jul 9, 2018

Automation for azure-sdk-for-ruby

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

@AutorestCI
Copy link

AutorestCI commented Jul 9, 2018

Automation for azure-sdk-for-node

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

@AutorestCI
Copy link

AutorestCI commented Jul 9, 2018

Automation for azure-sdk-for-java

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

@natinimni
Copy link
Contributor Author

@brjohnstmsft

@natinimni
Copy link
Contributor Author

@mhko

@natinimni
Copy link
Contributor Author

@abhishek225

@mhko
Copy link
Member

mhko commented Jul 9, 2018

Shouldn't this feature be in preview version?

@natinimni
Copy link
Contributor Author

natinimni commented Jul 9, 2018

This feature doesn't need to be in a preview version as it is backward compatible due to the following:

  1. One can request identity to be assigned to a previously created service
  2. If a service with an identity is being updated but the identity field is missing, the identity will not be deleted

@mhko
Copy link
Member

mhko commented Jul 10, 2018

Thanks, Nati. LGTM

@jhendrixMSFT jhendrixMSFT merged commit e97dba0 into Azure:master Jul 10, 2018
"enum": [
"SystemAssigned"
],
"x-ms-enum": {

Choose a reason for hiding this comment

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

as discussed, let's see if we really need this

"principalId": {
"readOnly": true,
"type": "string",
"description": "The principal ID of resource identity."
Copy link
Member

Choose a reason for hiding this comment

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

The principal ID of the resource identity.

"tenantId": {
"readOnly": true,
"type": "string",
"description": "The tenant ID of resource."
Copy link
Member

Choose a reason for hiding this comment

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

The tenant ID of the resource.

},
"type": {
"type": "string",
"description": "The identity type.",
Copy link
Member

Choose a reason for hiding this comment

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

Is there more detail we can add here so the generated documentation will be more self-explanatory?

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.

6 participants