We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi there,
your documentation for akamai_edge_hostname (https://techdocs.akamai.com/terraform/docs/pm-rc-edge-hostname) (for v4.6) suggest three possible values for ip_behavior
akamai_edge_hostname
ip_behavior
But IPV6_IPV4_DUALSTACK gives an error, I must use IPV6_COMPLIANCE.
IPV6_IPV4_DUALSTACK
IPV6_COMPLIANCE
This fails:
resource "akamai_edge_hostname" "edition-issues" { contract_id = var.contract_id group_id = var.group_id product_id = var.product.product_id ip_behavior = "IPV6_IPV4_DUALSTACK" edge_hostname = local.edge_hostname }
This works:
resource "akamai_edge_hostname" "edition-issues" { contract_id = var.contract_id group_id = var.group_id product_id = var.product.product_id ip_behavior = "IPV6_COMPLIANCE" edge_hostname = local.edge_hostname }
With IPV6_IPV4_DUALSTACK, I get this error:
Error: creating edge hostname: struct validation: IPVersionBehavior: must be a valid value
The text was updated successfully, but these errors were encountered:
Hi @rolmo ,
Thanks for reporting this issue. I will create internal ticket to fix our documentation.
BR, Lukasz
Sorry, something went wrong.
No branches or pull requests
Hi there,
your documentation for
akamai_edge_hostname
(https://techdocs.akamai.com/terraform/docs/pm-rc-edge-hostname) (for v4.6) suggest three possible values forip_behavior
But
IPV6_IPV4_DUALSTACK
gives an error, I must useIPV6_COMPLIANCE
.Terraform and Akamai Terraform Provider Versions
Affected Resource(s)
akamai_edge_hostname
Terraform Configuration Files
This fails:
This works:
Error Output
With
IPV6_IPV4_DUALSTACK
, I get this error:The text was updated successfully, but these errors were encountered: