Skip to content

Expose new API to download pre-generated vpn profile package URL#1557

Merged
olydis merged 2 commits intoAzure:currentfrom
ritwikbasu:current
Aug 25, 2017
Merged

Expose new API to download pre-generated vpn profile package URL#1557
olydis merged 2 commits intoAzure:currentfrom
ritwikbasu:current

Conversation

@ritwikbasu
Copy link
Copy Markdown
Contributor

@ritwikbasu ritwikbasu commented Aug 17, 2017

Expose new API to download pre-generated vpn profile package URL

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

Expose new API to download pre-generated vpn profile package URL
@azuresdkciprbot
Copy link
Copy Markdown

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/network/resource-manager/readme.md
Before the PR: Warning(s): 151 Error(s): 84
After the PR: Warning(s): 151 Error(s): 84

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

@olydis olydis added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Aug 21, 2017
@olydis
Copy link
Copy Markdown
Contributor

olydis commented Aug 21, 2017

@ravbhatnagar New operation.

@ritwikbasu
Copy link
Copy Markdown
Contributor Author

@ravbhatnagar - Can you please approve this PR or let me know if you have any concerns? This is one of our Ignite deliverables and we need this change to go in before proceeding with SDK/PS coding.

@ravbhatnagar
Copy link
Copy Markdown
Contributor

@ritwikbasu - this API wont work. Please schedule a 15 min sync with me on Wednesday to go over why.

Incorporate review comments
@azuresdkciprbot
Copy link
Copy Markdown

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/network/resource-manager/readme.md
Before the PR: Warning(s): 151 Error(s): 84
After the PR: Warning(s): 151 Error(s): 84

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

"$ref": "#/parameters/SubscriptionIdParameter"
}
],
"responses": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please define the model for the response instead of just marking it as string. Since the change has already gone in on the service side, please consider it in the next api version rev. Not blocking on it for now.

Copy link
Copy Markdown
Contributor

@ravbhatnagar ravbhatnagar left a comment

Choose a reason for hiding this comment

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

Just the one note that i added which NRP will consider fixing in the next api-version rev.

@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 Aug 25, 2017
@ravbhatnagar
Copy link
Copy Markdown
Contributor

@olydis - ARM signed off.

@olydis olydis merged commit 4c93570 into Azure:current Aug 25, 2017
@AutorestCI
Copy link
Copy Markdown

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

@AutorestCI
Copy link
Copy Markdown

@AutorestCI
Copy link
Copy Markdown

mccleanp pushed a commit that referenced this pull request Mar 23, 2022
* Update Datadog swagger

* Add liftr resource

* Remove some description
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.

9 participants