Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Terraform CLI and Terraform IBM Provider Version
terraform1.5
Installed ibm-cloud/ibm v1.58.0
Using schematics workspaces on IBM cloud
Affected Resource(s)
ibm_code_engine_job
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
I'll try to get a fix in as soon as I can. Unfortunately it might be a while until it is in. In case I find a workaround, I'll message you.
Thanks for reporting.
Community Note
Terraform CLI and Terraform IBM Provider Version
terraform1.5 Installed ibm-cloud/ibm v1.58.0
Using schematics workspaces on IBM cloud
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
Error: CreateJobWithContext failed Bad payload - The field 'scale_max_execution_time' is invalid. reason: INVALID
Panic Output
Expected Behavior
When using
run_mode = daemon
, it should not set any default values forscale_max_execution_time
andscale_retry_limit
.Documentation for the run_mode ibm_code_engine_job resource
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
None
References
It looks like
scale_max_execution_time
's schema validation code just puts it as a default value, regardless of the value of run_modeSame for
scale_retry_limit
's schema validation code