-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: check_certificate_revocation_status ignored on aws_networkfirewall_tls_inspection_configuration #38690
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.67.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Terraform Core Version
1.6.3
AWS Provider Version
5.61.0
Affected Resource(s)
Expected Behavior
Expected Certificate revocation status to be Enabled after
terraform apply
, or receive an error indicating what to fix in the HCL configuration.Actual Behavior
Expected Certificate revocation status is Disabled,
terraform apply
succeeds.Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Debug Output
N/A
Panic Output
N/A
Important Factoids
N/A
References
N/A
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: