Terraform Aws Ecs Web App Versions Save

Terraform module that implements a web app on ECS and supports autoscaling, CI/CD, monitoring, ALB integration, and much more.

2.1.0

1 week ago

🚀 Enhancements

fix: updated alb ingress module to the latest version @vsamofal (#274)

what

Just update alb version module, I need it mostly because this target group name limit is killing

why

Sounds like a good idea to keep it up to date as well

references

No issue for this, it super simple update, I tested it on my setup so it should be fine, but will see when all tests passes

🤖 Automatic Updates

Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#273)

what

  • Update workflows (.github/workflows) to add issue: write permission needed by ReviewDog tflint action

why

  • The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @osterman (#270)

what

  • Update workflows (.github/workflows/settings.yaml)

why

  • Support new readme generation workflow.
  • Generate banners

2.0.2

1 month ago
chore: add load_balancing_algorithm_type variable @dmitrijn (#236)

what

  • add load_balancing_algorithm_type variable for alb-ingress module

why

  • allow to switch between round_robin and least_outstanding_requests for alb target groups

🤖 Automatic Updates

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#265)

what

  • Install latest GitHub Action Workflows

why

  • Use shared workflows from cldouposse/.github repository
  • Simplify management of workflows from centralized hub of configuration

2.0.1

1 month ago

🤖 Automatic Updates

chore(deps): update terraform cloudposse/ecr/aws to v0.41.0 (main) @renovate (#257)

This PR contains the following updates:

Package Type Update Change
cloudposse/ecr/aws (source) module minor 0.34.0 -> 0.41.0

Release Notes

cloudposse/terraform-aws-ecr (cloudposse/ecr/aws)

v0.41.0

Compare Source

Allow to use ECR replication @​dmitrijn (#​103)

Closes https://github.com/cloudposse/terraform-aws-ecr/issues/99

v0.40.1

Compare Source

Allow cache though enabled repositories to fetch image from upstream @​mfuhrmeisterDM (#​117)

what

Add a principal list (principals_pull_though_access) which are allowed to use specific repositories as pull through cache (import images from upstream). This holds for repositories where one of the strings in prefixes_pull_through_repositories is a prefix of the repository name.

why

We are using ecr-public pull through cache and we want also new images to be downloaded automatically to the cache. Allowed principals for respective repos can use it with the newly introduced variables.

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​116)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

Update README.md and docs @​cloudpossebot (#​115)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

Update README.md and docs @​cloudpossebot (#​114)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.40.0

Compare Source

feat: support scan_type @​dudymas (#​113)

what

  • add scanning_configuration as child module

why

  • support scan_type settings
  • should be deployed as a per-account global, rather than per-ecr-repo

Notes

v0.39.0

Compare Source

feat: add organizations as readonly access @​dragosmc (#​106)

what

  • Add the ability to have organizations as trustees (read-only) for the ECR repository

why

  • As described in #​82 , it's sometimes useful to allow an entire organization to consume images from a centralized repository

references

v0.38.0

Compare Source

fix: cleans up principals lambda logic to separate policy doc @​Gowiem (#​105)

what

  • Clean up of the logic surrounding the var.principals_lambda policies

why

  • When this was originally implemented it was copy / pastad across multiple policy docs, which isn't necessary and creates a bunch of bloat.

references

v0.37.0

Compare Source

add optional policy allowing push access @​kpankonen (#​98)

what

  • adds the ability to give push-only access to the repository

why

  • full access was more than we wanted in our situation (CI pushing images to the repo) so we added a principals_push_access to give push-only access.

references

  • policy is based on this AWS doc
Sync github @​max-lobur (#​104)

Sync github from the template

v0.36.0

Compare Source

  • No changes

v0.35.0

Compare Source

adding force_delete @​pcartas (#​101)

Hi! im adding "force_delete" parameter, is implemented in aws 4.22.0 for an easier delete of the ecr

references

https://registry.terraform.io/providers/hashicorp/aws/4.22.0/docs/resources/ecr_repository

git.io->cloudposse.tools update @​dylanbannon (#​95)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

  • DEV-143

2.0.0

1 month ago
Update Terraform cloudposse/ecs-codepipeline/aws to v0.33.0 @adamantike (#225)

Breaking changes

This release introduces a breaking change that affects projects using the github_webhooks_token variable.

Since Terraform 1.2.0, modules to be used with the for_each, count, and depends_on arguments must not contain their own provider configurations. The github_webhooks_token variable was being used to instantiate a github provider, which must now be instantiated and provided separately.

If your project is affected by this change, the following steps will allow you to upgrade to this version:

  1. Add the GitHub provider to your project:

    terraform {
      required_providers {
        github = {
          source  = "integrations/github"
          version = ">= 4.2.0"
        }
      }
    }
    
  2. Instantiate the provider (feel free to use any other supported Authentication mechanism):

    provider "github" {
      owner = var.repo_owner
      token = "{your_github_token}"
    }
    
  3. Stop providing the github_webhooks_token variable to this module.

what

  • Removed variables no longer available in the cloudposse/ecs-codepipeline/aws module.
  • Supersedes #202
  • Fixes #227

why

  • Version 0.32.0 upgrades the cloudposse/repository-webhooks/github module, which removed the hardcoded github provider, so some variables have been removed in favor of instantiating the provider separately.

references

🤖 Automatic Updates

Add GitHub Settings @osterman (#255)

what

  • Install a repository config (.github/settings.yaml)

why

  • Programmatically manage GitHub repo settings
Update Scaffolding @osterman (#249)

what

  • Reran make readme to rebuild README.md from README.yaml
  • Migrate to square badges
  • Add scaffolding for repo settings and Mergify

why

  • Upstream template changed in the .github repo
  • Work better with repository rulesets
  • Modernize look & feel

1.8.2

2 months ago
git.io->cloudposse.tools update @dylanbannon (#193)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

  • DEV-143

1.8.1

1 year ago

🚀 Enhancements

fix: resource `aws_cloudwatch_log_group` should respect the context.enabled flag @bartelemi (#182)

what

  • Check the context flag as well as the cloudwatch_log_group_enabled flag to provision CW log group.
  • Additionally, add the same check before calls to coalesce functions that rely on null-label module. If the context is disabled, the label module will return null and call to coalesce will fail.

why

  • To destroy/disable this module we have to set two flags when only one should be enough

references

  • #181

1.8.0

1 year ago
feat: add deployment minimum healthy/maximum percent variable @mschfh (#221)

what

This PR exposes the deployment_maximum_percent and deployment_minimum_healthy_percent variables from cloudposse /ecs-alb-service-task

references

https://github.com/cloudposse/terraform-aws-ecs-alb-service-task#input_deployment_maximum_percent

1.7.0

1 year ago
feat: add ecs_security_group_enabled variable @WaylandAce (#218)

what

  • Add ecs_security_group_enabled variable to be able skip security group creation.

why

  • This change is required in case, when security group is managed outside of this module.

1.6.0

1 year ago
option to disable codepipeline but allow to keep ecr @mihaiplesa (#210)

what

why

  • we'd like to not create CodePipeline resources when codepipeline_enabled is false
  • give the option to keep the ECR repo, especially if it already has container images that are pushed without using GitHub Actions or something else

references

1.5.0

1 year ago
Add ecs_service_arn output @mschfh (#217)

what

  • This PR adds the ecs_service_arn output from ecs-alb-service-task

why

  • Required for an IAM policy

references

https://github.com/cloudposse/terraform-aws-ecs-alb-service-task/tree/master#output_service_arn