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

typo negationConditon in webapplicationfirewall #6104

Open
nschonni opened this issue May 24, 2019 · 2 comments
Open

typo negationConditon in webapplicationfirewall #6104

nschonni opened this issue May 24, 2019 · 2 comments
Labels
Network - Application Gateway Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@nschonni
Copy link
Contributor

Added in the February 2019 release, and also in the April release.
It's a server side bug rather than a swagger one #5341 (comment)
Conditon -> Condition

@jhendrixMSFT
Copy link
Member

Hopefully this can be fixed in the next API version.

nschonni added a commit to nschonni/azure-rest-api-specs that referenced this issue May 29, 2019
kpajdzik pushed a commit that referenced this issue May 31, 2019
* chore: Suppress Conditon in April Network WAF

Related to #6104

* chore: Cleanup passing cSpell exceptions

* chore: Update EditorConfig to match existing format
nschonni added a commit to nschonni/azure-rest-api-specs that referenced this issue Jun 5, 2019
@akning-ms akning-ms added the Service Attention Workflow: This issue is responsible by Azure service team. label Apr 26, 2020
@ghost
Copy link

ghost commented Apr 26, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub.

mccleanp pushed a commit that referenced this issue Mar 23, 2022
…#6104)

* target and solution objects are not editable in solutioninstance patch operation

* Update response codes for async operations to match the specification.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Network - Application Gateway Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

6 participants