Add Terraform V4 Support (and Graviton) #53
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…aws-serverless-static-wordpress into terraform_aws_v4
…aws-serverless-static-wordpress into terraform_aws_v4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm terrible at working on individual features in PRs, so in this one we have bundled, in no particular order:
Upgrade to V4 of AWS Terraform Provider.
Added support for Graviton-based CodeBuild
Added support for Graviton-based ECS Fargate (with automatic fallback to non-graviton if region doesn't support it)
Added healthCheck block to ECS Task Definition
Added in EventBrige monitoring for ECS Service Action events (which captures placement failures when using FARGATE_SPOT) capacity provider.