-
Notifications
You must be signed in to change notification settings - Fork 5.6k
[Hub Generated] Review request for FrontDoor WAF to add version 2019-03-01 stable #5918
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
[Hub Generated] Review request for FrontDoor WAF to add version 2019-03-01 stable #5918
Conversation
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-jsA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaEncountered a Subprocess error: (azure-sdk-for-java)
Command: ['/usr/local/bin/autorest', '/tmp/tmpvbvpisrt/rest/specification/frontdoor/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmpi77i7yhf'] AutoRest code generation utility [version: 2.0.4283; node: v8.12.0]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Failure:
Error: Unable to start AutoRest Core from /root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core
Error: Unable to start AutoRest Core from /root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core
at main (/opt/node_modules/autorest/dist/app.js:232:19)
at <anonymous>
/root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core/dist/app.js:33
autorest_core_1.Shutdown();
^
ReferenceError: autorest_core_1 is not defined
at process.on (/root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core/dist/app.js:33:5)
at emitOne (events.js:121:20)
at process.emit (events.js:211:7)
at process.emit (/node_modules/source-map-support/source-map-support.js:439:21)
fs.js:612
return binding.close(fd);
^
Error: EBADF: bad file descriptor, close
at Object.fs.closeSync (fs.js:612:18)
at StaticVolumeFile.shutdown (/opt/node_modules/autorest/dist/static-loader.js:352:10)
at StaticFilesystem.shutdown (/opt/node_modules/autorest/dist/static-loader.js:406:17)
at process.exit.n [as exit] (/opt/node_modules/autorest/dist/static-loader.js:169:11)
at printErrorAndExit (/node_modules/source-map-support/source-map-support.js:423:11)
at process.emit (/node_modules/source-map-support/source-map-support.js:435:16)
at process._fatalException (bootstrap_node.js:391:26) |
|
Can one of the admins verify this patch? |
REST Spec PR 'Azure/azure-rest-api-specs#5918' REST Spec PR Author 'eschwabe' REST Spec PR Last commit
Automation for azure-sdk-for-netA PR has been created for you: |
...n/frontdoor/resource-manager/Microsoft.Network/stable/2019-04-01/webapplicationfirewall.json
Show resolved
Hide resolved
|
@sergey-shandar Could you please review the PR and let me know if any additional sign-offs are required to release this API as stable. Thanks! |
specification/frontdoor/resource-manager/Microsoft.Network/stable/2019-03-01/network.json
Outdated
Show resolved
Hide resolved
...n/frontdoor/resource-manager/Microsoft.Network/stable/2019-03-01/webapplicationfirewall.json
Outdated
Show resolved
Hide resolved
...n/frontdoor/resource-manager/Microsoft.Network/stable/2019-03-01/webapplicationfirewall.json
Outdated
Show resolved
Hide resolved
REST Spec PR 'Azure/azure-rest-api-specs#5918' REST Spec PR Author 'eschwabe' REST Spec PR Last commit
|
@sergey-shandar - Could you please review the latest commit? Thanks! |
|
I did check with Eric (who created PR). There is no breaking change.. Adding new api with just minor updates in the new api vesrion (Compare iteration 1 and 7, for WebApplicationFirewall.json) |
SDK Automation [Logs] (Generated from 36e3078)
|
The AzureFrontDoor Service is planning to release the 2019-03-01 WAF API as stable. This PR contains minor validation and documentation changes.
Changes:
If you are a MSFT employee you can view your work branch via this link.
Contribution checklist: