Skip to content

Conversation

@promoisha
Copy link
Contributor

@promoisha promoisha commented Mar 2, 2018

Issues resource with Comments and Attachments subresources were added under theAPI resource.

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

@olydis olydis added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Mar 2, 2018
@olydis
Copy link
Contributor

olydis commented Mar 2, 2018

@ravbhatnagar new operations

@AutorestCI
Copy link

AutorestCI commented Mar 2, 2018

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@promoisha promoisha force-pushed the glfeokti_issues_resource branch from 6baa209 to f164fc7 Compare March 2, 2018 00:47
@promoisha
Copy link
Contributor Author

@solankisamir

@AutorestCI
Copy link

AutorestCI commented Mar 2, 2018

Automation for azure-sdk-for-go

Encountered a Subprocess error: (azure-sdk-for-go)

Command: ['/usr/local/bin/autorest', '/tmp/tmpm5vf3ydx/rest/specification/apimanagement/resource-manager/readme.md', '--go', '--go-sdk-folder=/tmp/tmpm5vf3ydx/sdk', '--multiapi', '[email protected]/autorest.go@~2.1.95', '--use-onever', '--verbose']
Finished with return code 1
and output:

AutoRest code generation utility [version: 2.0.4259; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
   Loading AutoRest core      '/tmp/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4259)
   Loading AutoRest extension '@microsoft.azure/autorest.go' (~2.1.95->2.1.95)
   Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.38->2.3.38)
Processing batch task - {"tag":"package-2017-03"} .
Processing batch task - {"tag":"package-2016-10"} .
Processing batch task - {"tag":"package-2016-07"} .
FATAL: swagger-document/compose - FAILED
FATAL: Error: '$.parameters.SubscriptionIdParameter.description' has incompatible values (---
  -
  Subscription credentials which uniquely identify Microsoft Azure subscription.
  The subscription ID forms part of the URI for every service call.
, ---
  -
  Subscription credentials which uniquely identify the Microsoft Azure
  subscription. The subscription ID forms part of the URI for every service
  call.
).
Process() cancelled due to exception : '$.parameters.SubscriptionIdParameter.description' has incompatible values (---
  -
  Subscription credentials which uniquely identify Microsoft Azure subscription.
  The subscription ID forms part of the URI for every service call.
, ---
  -
  Subscription credentials which uniquely identify the Microsoft Azure
  subscription. The subscription ID forms part of the URI for every service
  call.
).
Failure during batch task - {"tag":"package-2016-07"} -- Error: '$.parameters.SubscriptionIdParameter.description' has incompatible values (---
  -
  Subscription credentials which uniquely identify Microsoft Azure subscription.
  The subscription ID forms part of the URI for every service call.
, ---
  -
  Subscription credentials which uniquely identify the Microsoft Azure
  subscription. The subscription ID forms part of the URI for every service
  call.
)..
  Error: '$.parameters.SubscriptionIdParameter.description' has incompatible values (---
  -
  Subscription credentials which uniquely identify Microsoft Azure subscription.
  The subscription ID forms part of the URI for every service call.
, ---
  -
  Subscription credentials which uniquely identify the Microsoft Azure
  subscription. The subscription ID forms part of the URI for every service
  call.
).

@promoisha promoisha force-pushed the glfeokti_issues_resource branch 2 times, most recently from 5d9e129 to 0950562 Compare March 2, 2018 00:55
@promoisha promoisha force-pushed the glfeokti_issues_resource branch from 0950562 to bf2a1ed Compare March 2, 2018 03:45
@promoisha
Copy link
Contributor Author

Hi, @ravbhatnagar! Could you please take a look? Thanks!

@ravbhatnagar
Copy link
Contributor

Looks good. Signing off from ARM side.

@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 Mar 8, 2018
@promoisha
Copy link
Contributor Author

@olydis Don't merge this PR, as the API is not out yet.

Copy link
Contributor

@olydis olydis left a comment

Choose a reason for hiding this comment

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

Looking good overall, just one likely bug and some minor suggestions! 🙂 On which date is this API going live?

"in": "body",
"required": true,
"schema": {
"$ref": "#/definitions/IssueAttachmentPutContract"
Copy link
Contributor

Choose a reason for hiding this comment

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

Just a non-technical suggestion: I'd not put "Put" in the name of this class, it's a technical detail of the API and not helpful to SDK users. Unfortunately, I thing there is no big consensus for naming these things, but I've seen things like "...Setting" or "...Parameters" before (where "..." is the underlying resource type, i.e. IssueAttachmentContract in this case). Maybe you can take a quick look at other "put" operations in this RP to find the common naming strategy 🙂

],
"description": "Issue contract Properties."
},
"IssueCommentCollection": {
Copy link
Contributor

Choose a reason for hiding this comment

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

Applies to all ...Collection types: Could you mark all properties as readOnly: true?

],
"description": "Issue Attachment Contract details."
},
"IssueAttachmentPutContractProperties": {
Copy link
Contributor

Choose a reason for hiding this comment

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

not used anywhere - thanks to the example you provided for the put operation, this was caught by our tooling 😃 Pretty sure you wanted to use this schema for IssueAttachmentPutContract's properties. (My naming comment regarding using "Put" in the name of this type of course also applies for this type)

@olydis
Copy link
Contributor

olydis commented Mar 20, 2018

@promoisha please respond to outstanding comments/questions. Will otherwise close this PR due to inactivity (can be reopened once you are ready to move forward).

@olydis olydis added the Reviewed-ChangesRequested <valid label in PR review process>add this label when assignee request changes after review label Mar 21, 2018
@olydis
Copy link
Contributor

olydis commented Mar 23, 2018

@salameer @promoisha Closing due to inactivity. Feel free to reopen once you're ready to address outstanding issues.

@olydis olydis closed this Mar 23, 2018
@AutorestCI
Copy link

AutorestCI commented Mar 23, 2018

Automation for azure-libraries-for-java

Nothing to generate for azure-libraries-for-java

@AutorestCI
Copy link

AutorestCI commented Mar 23, 2018

Automation for azure-sdk-for-node

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

@olydis
Copy link
Contributor

olydis commented Mar 29, 2018

@promoisha Is this API already public/live or when is that going to happen? Just so I can merge at the right point in time 🙂

Copy link
Contributor

@olydis olydis left a comment

Choose a reason for hiding this comment

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

LGTM! Will merge once you confirmed whether/when this is live 🙂

@olydis olydis added Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates and removed Reviewed-ChangesRequested <valid label in PR review process>add this label when assignee request changes after review labels Mar 29, 2018
@promoisha
Copy link
Contributor Author

@olydis it's hitting the production right now, so I assume it's safe to merge :). Thanks a lot!

@olydis
Copy link
Contributor

olydis commented Mar 29, 2018

@promoisha Thank you!

@olydis olydis merged commit e4b3652 into Azure:master Mar 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates 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.

4 participants