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

WAF Profile request_body_enforcement documentation is against wrong resource #27290

Closed
1 task done
rlaveycal opened this issue Sep 5, 2024 · 2 comments · Fixed by #27303
Closed
1 task done

WAF Profile request_body_enforcement documentation is against wrong resource #27290

rlaveycal opened this issue Sep 5, 2024 · 2 comments · Fixed by #27303

Comments

@rlaveycal
Copy link

rlaveycal commented Sep 5, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

1.9

AzureRM Provider Version

4.0

Affected Resource(s)/Data Source(s)

azurerm_web_application_firewall_policy

Terraform Configuration Files

N/A

Debug Output/Panic Output

N/A

Expected Behaviour

The azurerm_web_application_firewall_policy resource's request_body_enforcement property should be documented.

Actual Behaviour

The request_body_enforcement property documentation was added to the application_gateway resource (see PR link)

Steps to Reproduce

No response

Important Factoids

No response

References

#27094

sinbai added a commit to sinbai/terraform-provider-azurerm that referenced this issue Sep 6, 2024
@sinbai
Copy link
Contributor

sinbai commented Sep 6, 2024

Hi @rlaveycal thanks for raising this issue. PR has been submitted to fix this doc issue.

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants