#WAF Add extended WAF functionality to Application Gateway#1052
Conversation
|
@jobatzil, |
There was a problem hiding this comment.
@jobatzil As I can see. This PR may contain some breaking changes and CI still reports some errors/warnings which are not related to the changes. Do you have a link to previous PR where the errors/warnings have been discussed? https://travis-ci.org/Azure/azure-rest-api-specs/jobs/213495817
| "required": [ | ||
| "enabled" | ||
| "enabled", | ||
| "firewallMode", |
There was a problem hiding this comment.
It's a breaking change.
There was a problem hiding this comment.
Yes, it's adding some new functionality to the web application firewall.
We introduce it for the new Api-Version 2017-03-01 and no older ones though.
There was a problem hiding this comment.
you have to release the sdk on a major version.
There was a problem hiding this comment.
It looks like no SDK was published with this api-version yet (please, confirm). So it should be ok to publish. Of course, we still have to address the warnings/errors.
There was a problem hiding this comment.
The azure-sdk-for-net PR is currently still open since we have to coordinate multiple Network related PRs. I will changed the Version to a new major version as @DeepakRajendranMsft requested.
There was a problem hiding this comment.
@sergey-shandar Yes, no SDK with api-version 2017-03-01 was published yet
|
@sergey-shandar We will address the CI warnings later, but don't have time rn since we want to get into the upcoming release of PowerShell. |
| "health": { | ||
| "type": "string", | ||
| "description": "Health of backend server. Possible values are: 'Unknown', 'Up', 'Down', and 'Partial'.", | ||
| "description": "Health of backend server.", |
There was a problem hiding this comment.
why are you changing the description
There was a problem hiding this comment.
i believe the documentation team did this
There was a problem hiding this comment.
It get's automatically added to the auto-generated code. Otherwise the possible enum values would be twice in a row in the documentation of the property.
| "required": [ | ||
| "enabled" | ||
| "enabled", | ||
| "firewallMode", |
There was a problem hiding this comment.
you have to release the sdk on a major version.
| }, | ||
| "ruleSetType": { | ||
| "type": "string", | ||
| "description": "The type of the web application firewall rule set. Possible values are: 'OWASP'." |
There was a problem hiding this comment.
why not an enum?
There was a problem hiding this comment.
seems like the service is also not an enum
|
I will change the Version number in the azure-sdk-for-net to 10.0.0.0 |
|
@jobatzil @salameer @veronicagg Ok, here's a list of errors/warnings which we need to discuss
Some other warnings and errors are derived from the network.json swagger file. |
|
@sergey-shandar I can change the warnings that are related to the code I'm adding, but would prefer to leave the other warnings for this PR since some of them may introduce further breaking changes. |
|
SDKViolation:
RPCViolation:
-DefinitionsPropertiesNamesCamelCase, 636, 640, 656, 740, 865, 1122, 1143, 740
|
|
Generated SDK Azure/azure-sdk-for-net#2992 |
|
@ravbhatnagar there are several cases when Operations API is not implemented because there are several APIs (swaggers) implemented by this service. Could you provide guidance how to provide the Operations API using composite swagger? |
sergey-shandar
left a comment
There was a problem hiding this comment.
Please, address the errors/warnings in the next major version so we can get rid of them.
|
No modification for NodeJS |
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
api-versionin the path should match theapi-versionin the spec).Quality of Swagger