There's a terraform ordering problem where the forced deployment can be created while terraform is still making other changes to the API, so those changes are not included in the deployment snapshot. This can probably be hacked around with depends_on but that feels brittle to maintain. What I want is a way to force the deployment to always happen last (after all other APIG/lambda changes are complete).
There's a terraform ordering problem where the forced deployment can be created while terraform is still making other changes to the API, so those changes are not included in the deployment snapshot. This can probably be hacked around with
depends_onbut that feels brittle to maintain. What I want is a way to force the deployment to always happen last (after all other APIG/lambda changes are complete).