Skip to content

Conversation

@dosegal
Copy link
Contributor

@dosegal dosegal commented Jul 17, 2019

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@AutorestCI
Copy link

AutorestCI commented Jul 17, 2019

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Jul 17, 2019

Automation for azure-sdk-for-go

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

@AutorestCI
Copy link

AutorestCI commented Jul 17, 2019

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@nschonni
Copy link
Contributor

You can add the extra words to https://github.com/Azure/azure-rest-api-specs/blob/master/custom-words.txt if they're correct

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jul 17, 2019

In Testing, Please Ignore

[Logs] (Generated from be784b1, Iteration 9)

Succeeded Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
Warning Python: Azure/azure-sdk-for-python [Logs] [Diff]
  • No packages generated.
Warning JavaScript: Azure/azure-sdk-for-js [Logs] [Diff]
  • No packages generated.

@dosegal dosegal marked this pull request as ready for review July 22, 2019 12:04
@dosegal
Copy link
Contributor Author

dosegal commented Jul 22, 2019

@shahabhijeet please review, thanks

@dosegal
Copy link
Contributor Author

dosegal commented Jul 28, 2019

@shahabhijeet is there any update?

@majastrz majastrz added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Jul 29, 2019
Copy link
Member

@majastrz majastrz left a comment

Choose a reason for hiding this comment

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

Looks good from ARM side.

@dosegal
Copy link
Contributor Author

dosegal commented Jul 30, 2019

@shahabhijeet @praries880 can someone please review the PR? thanks

Copy link
Contributor

@mmyyrroonn mmyyrroonn left a comment

Choose a reason for hiding this comment

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

LGTM. I just want to confirm. Lot's of parameters set readOnly field to true. Usually, readOnly: true means these parameters should not appear in the PUT/PATCH methods. These parameters are set by design. Right?

"readOnly": true,
"description": "The graph item display name which is a short humanly readable description of the graph item instance. This property is optional and might be system generated."
},
"additionalData": {
Copy link
Contributor

Choose a reason for hiding this comment

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

This field is a little bit tricky. What's kind of additionalData we want?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

additionalData can hold any custom field that should be part of the "entity" object. The fields don't share the same type, so this is why the type of "additionalProperties" is object.

@shahabhijeet
Copy link
Contributor

@myronfanqiu go ahead merge the PR if you are satisfied with responses to your comments.

@dosegal
Copy link
Contributor Author

dosegal commented Aug 2, 2019

LGTM. I just want to confirm. Lot's of parameters set readOnly field to true. Usually, readOnly: true means these parameters should not appear in the PUT/PATCH methods. These parameters are set by design. Right?

@myronfanqiu One of our resource types, called entities, supports only Get/Post operations in the server-side, and creation/modification is not allowed as part of the API. We have 15 different kinds of this resource, and they all share the same behavior. This is why you see many readOnly properties set to true.

@mmyyrroonn
Copy link
Contributor

@dosegal Thanks!

@mmyyrroonn mmyyrroonn merged commit 08aecef into Azure:master Aug 5, 2019
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.

7 participants