-
Notifications
You must be signed in to change notification settings - Fork 673
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
[ICD][Postgresql] Error updating database auto_scaling: Unprocessable Entity #4339
Comments
@ifs-anthonylecarrer Thank you for reaching out! Could you please set the logs to debug mode? You can do so as follows in the After doing so, please run your code again. You should hopefully see all the API calls being triggered in the logs. Then send them and we'll be able to better assist you :D Thank you and I apologize for the inconvenience. |
The provider 1.49 is working with the same code. Are u asking me to do your job and to test your provider ? |
@ifs-anthonylecarrer I'm asking you to provide the logs to help me support you. |
@ifs-anthonylecarrer auto_scaling was refactored to use a different client library in the last release so this does appear to be a change in behavior. The template provided is setting
{
"autoscaling": {
"disk": {
"scalers": {
"capacity": {
"enabled": false,
"free_space_less_than_percent": 0
},
"io_utilization": {
"enabled": false,
"over_period": "",
"above_percent": 0
}
},
"rate": {
"increase_percent": 0,
"period_seconds": 0,
"limit_mb_per_member": 0,
"units": ""
}
},
"memory": {
"scalers": {
"io_utilization": {
"enabled": false,
"over_period": "",
"above_percent": 0
}
},
"rate": {
"increase_percent": 0,
"period_seconds": 0,
"limit_mb_per_member": 0,
"units": ""
}
}
}
} Response
{
"errors": {
"autoscaling.rate.period_seconds": [
"must be greater than or equal to 60"
],
"disk.scalers.io_utilization.over_period": [
"must be one of [\"5m\", \"15m\", \"30m\", \"60m\"]" a user error
]
}
} I would suggest as an interim fix to modify the template to not set |
….50.0 [generating an 'Unprocessable Entity](IBM-Cloud/terraform-provider-ibm#4339) when passing a null auto scaling option (#74)
There are additional issues with the When setting the Folloing this a second apply (with no changes) results in:
which is another bug, since it was processable the first time and is suddenly no longer processable. Should the documentation for the cpu block be removed from the terraform ibm_database resource if it is not used and causes issues if is coded? Additionally the documentation is missing an entry for |
Just to add to @shemau's comment above, when you try and actually set the
If CPU auto scaling is not supported by ICD, then the documentation needs to be updated because clearly if you try to use it, things break. cc @alexhemard |
@ocofaigh Correct, there is no
@shemau Thanks for catching this! I'll try and get this fix prioritized |
Community Note
Terraform CLI and Terraform IBM Provider Version
terraform : 1.3
terraform ibmcloud provider : 1.50.0
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Panic Output
Expected Behavior
NO ERROR
Actual Behavior
Deploy failed
Steps to Reproduce
terraform apply -var-file validation-values.json
Important Factoids
References
The text was updated successfully, but these errors were encountered: