cloudposse/terraform-aws-ecs-alb-service-task v0.76.1

on GitHub

what

in attempt to fix apply time issues like #28070,
replace usage of function timestamp() with plantimestamp()

why

provided function apparently works for use cases when redeploy_on_apply && force_new_deployment set to true

references

• hashicorp/terraform-provider-aws#28070

• Update AWS account to fix this error:

Error:     Not equal: 
                   expected: "arn:aws:ecs:us-east-2:126450723953:cluster/eg-test-ecs-alb-service-task-ezatqz"
                   actual  : "arn:aws:ecs:us-east-2:799847381734:cluster/eg-test-ecs-alb-service-task-ezatqz"

why

• Terratests are failing due to assertions not validating with the expected account ID

references

• Failing Job

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub