Closed oscarsb66 closed 1 year ago
Hi @oscarsb66, We will start investigating this issue, looks like some API validation, but in mean time please provide some exemplary configuration file for which you have experienced this issue.
I had this same issue, I solved it by adding an empty value to the property
{
"name": "PROPETY_NAME",
"description": "My description",
"value": "", // <------
"hidden": false,
"sensitive": false
}
@oscarsb66 can you please try to reproduce it with latest Akamai Terraform Provider version?
Hi there,
Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
Debug Output
Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.
Panic Output
If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the
crash.log
.Expected Behavior
What should have happened?
Changing the weight of a datacenter of an existing gtm property.
Actual Behavior
What actually happened?
When changing the weight of a datacenter on an existing gtm property, it fails with the error above. We're only seeing this with one of our domains.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example: