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

Front Door publicpreview #3973

Merged
merged 9 commits into from
Sep 21, 2018
Merged

Front Door publicpreview #3973

merged 9 commits into from
Sep 21, 2018

Conversation

jmelvinwork
Copy link
Contributor

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

jmelvinwork and others added 2 commits September 20, 2018 13:12
@jmelvinwork
Copy link
Contributor Author

@keburek

@AutorestCI
Copy link

AutorestCI commented Sep 20, 2018

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@AutorestCI
Copy link

AutorestCI commented Sep 20, 2018

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Sep 20, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Sep 20, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@AutorestCI
Copy link

AutorestCI commented Sep 20, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@AutorestCI
Copy link

AutorestCI commented Sep 20, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@jmelvinwork
Copy link
Contributor Author

This was signed off in the internal repo already.

Copy link
Contributor

@KrisBash KrisBash left a comment

Choose a reason for hiding this comment

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

Sign off from ARM

@KrisBash KrisBash added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Sep 20, 2018
@jmelvinwork
Copy link
Contributor Author

@lmazuel Can you please review this today? We want to get this merged ASAP

ghost
ghost previously approved these changes Sep 21, 2018
@marstr marstr dismissed ghost ’s stale review September 21, 2018 16:58

@dashult requested that his review be dismissed offline, because he committed to fixing it himself later.

@jmelvinwork
Copy link
Contributor Author

The linter says the following:
_Potential new ARM errors

R3023 - OperationsAPIImplementation
Operations API must be implemented for '/providers/Microsoft.Network/operations'.
at specification/frontdoor/resource-manager/Microsoft.Network/preview/2018-08-01-preview/webapplicationfirewall.json:36_

But we are using NRP's Microsoft.Network/operations API, which is defined under /network/...
How do we fix this error?

…tions/ API

Add suppression for operationsAPIImplementation as we use NRP's operations/ API
@jmelvinwork
Copy link
Contributor Author

The linter says the following:

Potential new ARM errors
R3023 - OperationsAPIImplementation
Operations API must be implemented for '/providers/Microsoft.Network/operations'.
at specification/frontdoor/resource-manager/Microsoft.Network/preview/2018-08-01-preview/webapplicationfirewall.json:36

But we are using NRP's Microsoft.Network/operations API, which is defined under /network/...
How do we fix this error?

Laurent helped me out. Thanks, Laurent!

@jmelvinwork jmelvinwork reopened this Sep 21, 2018
@jmelvinwork
Copy link
Contributor Author

Did not mean to close PR! Sorry

Fix typo
Fix indentation
@@ -0,0 +1,19 @@
Stack trace:
Copy link
Member

Choose a reason for hiding this comment

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

Please remove that file.

jmelvinwork and others added 2 commits September 21, 2018 13:58
WebApplicationFirewallPolicy Swagger did not contain the return value ResourceState.
@lmazuel
Copy link
Member

lmazuel commented Sep 21, 2018

@jmelvinwork My last fixes fixed the CLI, and I think it's what you intended. Merging the PR since you told me you want it merge today.
Still, you own this, please double-check my commits and let me know if you have any concerns. Ideally, let me know if you don't have concerns too :)
Thanks!

@lmazuel lmazuel merged commit 5682ce2 into Azure:master Sep 21, 2018
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.

5 participants