Terraform definition does not perfectly record reality

[paul-butcher]

There is something awry in the terraform definition whereby either or both of these is true:

1. It does not contain some default values
2. It opaquely sets some values, regardless of the current value

As a result, terraform apply always has changes. Sometimes, there are changes to things like version numbers in AWS services that cause terraform to want to update certain configuration items, but this is not the case here.

To reproduce -

1. cd to a terraform directory (e.g. pipeline/terraform/2024-02-01)
2. terraform init
3. terraform plan
   • If this is an existing pipeline, set according to the tf definitions, it should say there is nothing to do.
   • It actually says 5 to add, 57 to change, 5 to destroy.
4. terraform apply (and yes to apply the change)
5. terraform plan again
   • The response is once again 5 to add, 57 to change, 5 to destroy.

[paul-butcher]

container_definitions in the scaling service forces replacement.

[paul-butcher]

Slack