Open stevendborrelli opened 1 year ago
this issue we need to fix in upjet ?
@haarchri yes, I believe it should be enforced there or at the XP level. Opened here to track the precise issue we encountered.
Related issue https://github.com/upbound/upjet/issues/78
The same happens also for kinesis Stream resource. Once, it's created, it cannot be destroyed with the same error: Instance cannot be destroyed Resource lifecycle.prevent_destroy set, but the plan calls for this resource to be destroyed. To avoid this error and continue with the plan, either disable lifecycle.prevent_destroy or reduce the scope of the plan using the -target flag.'
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
any update?
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
/fresh
What problem are you facing?
Changes made to a
IdentityProviderConfig
causes the resource to be stuck in alifecycle_destroy
state. The resource should either be immutable or allow the recreation (which is currently against the XRM spec):Causes a
lifecycle_destroy
error:ForceNew
<provider https://github.com/hashicorp/terraform-provider-aws/blob/f4b691325088fb6c4e7b3ae331884b3e681ff52f/internal/service/eks/identity_provider_config.go#L75C7-L75C7>How could Official AWS Provider help solve your problem?
Resources should check for
ForceNew
fields and either reject changes, or allow the user the option to recreate/destroy.