AWS Batch and AWS Step functions broken by terraform apply

Link512 · October 8, 2019, 12:08pm

I wasn’t saying it should be aware of logical level resources, I was suggesting that perhaps for resources that have revisions(like AWS Batch) it can have a flag to not automatically de-register a revision when “forcing” a new resource

Topic		Replies	Views
Terraform Destroyed Resources when doing batch deployments Terraform	1	348	September 29, 2021
Expression evaluating to 'true' if a resource has changed during that run Terraform	3	428	December 10, 2021
AWS Batch compute environment needs recreating after launch template change AWS	0	894	September 30, 2020
Second time apply without any change in code or manual console change causing force replacement AWS	7	3394	February 1, 2021
Apply previous state file or undo plan Terraform	5	13286	September 5, 2023

AWS Batch and AWS Step functions broken by terraform apply

Related topics