terraform-ibm-modules/terraform-ibm-base-ocp-vpc

Changing operating_system on existing cluster does not trigger a destroy and create

vburckhardt opened this issue · 4 comments

vburckhardt commented

This may need to be surfaced to provider

ocofaigh commented

@vburckhardt provider says This field only affects cluster creation:

operating_system - (Optional, String) The operating system of the workers in the default worker pool. For supported options, see Red Hat OpenShift on IBM Cloud version information or IBM Cloud Kubernetes Service version information. This field only affects cluster creation, to manage the default worker pool, create a dedicated worker pool resource.

So probably working as expected. Maybe we create enhancement request?

vburckhardt commented

@ocofaigh - I think a bug should be filed, as it's not consistent with the terraform common practices - it should attempt to destroy and recreate. It is up to the user of the provider to decide on the behavior, rather than the provider itself. https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle#ignore_changes change field exists for this reason.