bug: settings for ALB and ECS in template files are overwritten by LocalStack on deploy #10766
Open
1 task done
Labels
area: integration/terraform
Issues related to HashiCorp Terraform
status: backlog
Triaged but not yet being worked on
type: bug
Bug report
Is there an existing issue for this?
Current Behavior
Deploy Terraform stack to fresh LocalStack instance with
tflocal apply
. Run atflocal plan|apply
directly after, and observe listing of proposed changes to infrastructure despite no changes to template files.Expected Behavior
Deploy Terraform stack to fresh LocalStack instance with
tflocal apply
. Run atflocal plan|apply
directly after, and observe that no change is needed and no resources are updated.How are you starting LocalStack?
With the
localstack
scriptSteps To Reproduce
How are you starting localstack (e.g.,
bin/localstack
command, arguments, ordocker-compose.yml
)Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)
I've attached an archive with example template files that reproduce this behavior.
Archive.zip
Environment
Anything else?
It's unclear if this is intended behavior. If it is, there is a lack of documentation on what infrastructure configurations are typically overwritten on a deploy to LocalStack. It is also worth noting that after running a subsequent
tflocal apply
after the initial successful one, the application breaks and no new tasks start in the ECS service.Observed logs from LocalStack container when ECS service crashes:
The text was updated successfully, but these errors were encountered: