Provider doesn't track remote aws-auth configmap changes
Opened this issue · 0 comments
cilindrox commented
the readme states:
On each
terraform apply
, the provider compares the currentaws-auth
configmap against the desired configmap contents, and runeksctl create iamidentitymapping
to create additional mappings andeksctl delete iamidentitymapping
to delete redundant mappings.
I've noticed this doesn't track any remote CM modifications and leads to drift without ever modifying TF's state. eg:
terraform apply
a cluster config using this module.- modify aws-auth on the cluster via kubectl
terraform plan
- modifications to the remoteaws-auth
cm aren't noticed, and no changes to apply are reported by this provider.