Destroying and re-creating dependent Terraform modules when their parent changes #8
-
A user asked:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The best way to achieve this would be to set, for example, a name parameter in your child module (such as the This way, Terraform will consider the name change a destructive and backward incompatible change, causing the dependent resources to be destroyed and re-created as you intend. |
Beta Was this translation helpful? Give feedback.
The best way to achieve this would be to set, for example, a name parameter in your child module (such as the
worker_name_prefix
) in our eks workers module) to the version of CNI - or something similar that will change everytime that CNI is deployed.This way, Terraform will consider the name change a destructive and backward incompatible change, causing the dependent resources to be destroyed and re-created as you intend.