Skip to content
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

IoT Hub - X509CA support #1723

Merged
merged 8 commits into from
Sep 30, 2017
Merged

IoT Hub - X509CA support #1723

merged 8 commits into from
Sep 30, 2017

Conversation

mastermanu
Copy link
Contributor

@mastermanu mastermanu commented Sep 22, 2017

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

Copy link

@alvadb alvadb left a comment

Choose a reason for hiding this comment

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

There are multiple linter errors (https://travis-ci.org/Azure/azure-rest-api-specs/jobs/278476257). Please fix.

"$ref": "#/parameters/subscriptionId"
},
{
"name": "resourceGroupName",
Copy link

Choose a reason for hiding this comment

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

Please move this to the global parameter section and reference throughout.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

"type": "string"
},
{
"name": "resourceName",
Copy link

Choose a reason for hiding this comment

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

Please move this to the global parameter section and reference throughout.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

"type": "string"
},
{
"name": "certificateName",
Copy link

Choose a reason for hiding this comment

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

Please move this to the global parameter section and reference throughout.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

@mastermanu
Copy link
Contributor Author

@alvadb - Please see: #1514. (This was the previous PR, but the employee has left the company so I created a new PR). It was agreed that the Linter warnings do not apply in this particular instance and was signed off by Anu

@alvadb alvadb added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Sep 23, 2017
@ravbhatnagar
Copy link
Contributor

@mastermanu @manusr I don't see the changes that were requested in the older PR. Properties like subjectname etc should go inside the properties bag. Please make sure the certificate resource complies with the basic shape needed for an ARM resource. Since this is likely a proxy resource, it will have id, name and type properties and all other peoperties will go inside the properties bag

@Azure Azure deleted a comment from msftclas Sep 27, 2017
@azuresdkciprbot
Copy link

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/iothub/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 17
After the PR: Warning(s): 0 Error(s): 17

💡 Please review potentially introduced Error(s)/Warning(s): Analysis Report 💡

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/iothub/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 17
After the PR: Warning(s): 0 Error(s): 17

💡 Please review potentially introduced Error(s)/Warning(s): Analysis Report 💡

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@alvadb alvadb merged commit 1a9d396 into Azure:current Sep 30, 2017
@AutorestCI
Copy link

No modification for AutorestCI/azure-sdk-for-node

@AutorestCI
Copy link

@AutorestCI
Copy link

@@ -2138,6 +2441,28 @@
"description": "The version of the API.",
"required": true,
"type": "string"
},
"resourceGroupName": {
Copy link
Contributor

Choose a reason for hiding this comment

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

Choose a reason for hiding this comment

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

@amarzavery I've added "x-ms-parameter-location": "method" to the objects that describe parameters that are only used in methods, however I'm losing the "credentials" parameter IotHubClientConfiguration(credentials, subscription_id, base_url) has now become IotHubClientConfiguration(subscription_id, base_url) and this seems to be causing several issues. Any thoughts on how to fix this?

Copy link

@andrew-buckley andrew-buckley Oct 2, 2017

Choose a reason for hiding this comment

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

Ah seems to be an autorest option that might be new

"tags": [ "Certificates" ],
"summary": "Get the certificate list.",
"description": "Returns the list of certificates.",
"operationId": "Certificates_ListByIoTHub",

Choose a reason for hiding this comment

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

should be Certificates_ListByIotHub, autorest generated sdks are getting confused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants