-
Notifications
You must be signed in to change notification settings - Fork 542
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
Provider doesn't support the replay_protection value when creating a cloudflare_ipsec_tunnel #3235
Comments
Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of This issue has been marked with |
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
It appears the cloudflare-go module itself doesn't have Replay Protection defined in the struct. |
Appears to be related to an issue with the cloudflare-go module not supporting this attribute. PR has been submitted to add this functionality: |
Confirmation
Terraform and Cloudflare provider version
Affected resource(s)
Terraform configuration files
Link to debug output
n/a
Panic output
No response
Expected output
Expected ability to be able to configure
replay_protection
Actual output
Unable to configure
replay_protection
Steps to reproduce
replay_protection
valueAdditional factoids
The link below is to the Cloudflare terraform provider documentation. It appears that the provider doesn't support the ability to enable replay protection.
cloudflare_ipsec_tunnel | Resources | cloudflare/cloudflare | Terraform | Terraform Registry
You can see within the codebase itself, within the read function, it doesn't reference the replay_protection value
terraform-provider-cloudflare/internal/sdkv2provider/resource_cloudflare_ipsec_tunnel.go at master · cloudflare/terraform-provider-cloudflare (github.com)
You can see within the List IPsec Tunnels API call however that Cloudflare does expose it
Cloudflare API Documentation
References
No response
The text was updated successfully, but these errors were encountered: