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
% terraform -v Terraform v1.10.2 on darwin_arm64
Please list the affected resources, for example:
fastly_tls_subscription
resource "fastly_tls_subscription" "tls" { domains = nonsensitive(var.service.domain[*].name) certificate_authority = "lets-encrypt" }
I should have been aware at the planning stage that the resource required a configuration_id.
configuration_id was marked as optional, so there was no way for me to tell that it was required by the API
https://gist.github.com/nightpool/98410f3fcfe4cc27d0c0f5fd8441846a
Please list the steps required to reproduce the issue, for example:
terraform apply
It does not appear that we have a default TLS config set for our account:
% fastly tls-config list NAME ID BULK DEFAULT TLS PROTOCOLS HTTP PROTOCOLS DNS RECORDS <redacted> CbByLy3Rad5QJge6H7fKKA false false 1.0, 1.1, 1.2 http/1.1, http/2 <redacted> SHcxcEMSAPhBvrgIrAe3uA false false 1.2 http/1.1, http/2
The provider should be able to detect this and enforce a TLS configuration at plan time.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Terraform Version
Affected Fastly Terraform Resource(s)
Please list the affected resources, for example:
fastly_tls_subscription
Terraform Configuration Files
Expected Behavior
I should have been aware at the planning stage that the resource required a configuration_id.
Actual Behavior
configuration_id was marked as optional, so there was no way for me to tell that it was required by the API
https://gist.github.com/nightpool/98410f3fcfe4cc27d0c0f5fd8441846a
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids (optional)
It does not appear that we have a default TLS config set for our account:
The provider should be able to detect this and enforce a TLS configuration at plan time.
The text was updated successfully, but these errors were encountered: