github-actions[bot]
commented
5 months ago Community Note
Voting for Prioritization
- Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
- Please see our prioritization guide for information on how we prioritize.
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
- If you are interested in working on this issue, please leave a comment.
- If this would be your first contribution, please review the contribution guide.
Terraform Core Version
1.5.7
AWS Provider Version
5.40.0
Affected Resource(s)
aws_wafv2_web_acl
Expected Behavior
Once aws_wafv2_web_acl resource has been created and also bot control rule has been added, outputting the application integration url should be the proper URL for the sdk. It should also worked when given an existing WAF and bot control rule has been added.
Example: output "regional_waf_web_acl_challenge_sdk_url" { value = aws_wafv2_web_acl.webacl.application_integration_url }
Actual Behavior
When outputting the application_integration_url for a existing WAF with bot control enabled, the url seems to be evaluated eagerly rather than being computed once the actual url is available from aws. Re-running the apply command the 2nd time works as expected and the SDK URL is populated Example of first run:
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
N/A
Steps to Reproduce
terraform apply {some_module_waf}
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None