Optionally create github actions secrets with ECR details & creds

See #35 for details

ECR Scanning

This release contains a new flag for enabling 'scan_on_push'. When this is enabled then all images pushed to the repo are scanned for any security software vulnerabilities. This is set to 'true' by default.

The 'example/ecr.tf' template is also now enhanced to include an example of how to deploy a lambda function that will notifiy a given slack channel of the image scan results.

4.0

This release is terraform 0.12 upgrade for ECR module

Terraform 0.12.13 upgrade

DONOT USE until the release tag is tested with Cloud Platform environment pipeline.

3.4

In this release removed default ECR lifecycle policy, that will only keep the 100 most recent versions of an image.

Now there will be no lifecycle policy.

3.3

ECR repositories created for use in the Cloud Platform will have a default lifecycle policy applied.

In this version the default ECR lifecycle policy is set to 100, that will only keep the 100 most recent versions of an image.

3.2

This removes the need for the aws_region variable.

Providers now need to be defined outside of the module, and specified at module invocation.

The example now comes with two extra providers, one dedicated to eu-west-1 (ireland) and another to eu-west-2 (london).

The right provider to use has to be selected when the module is called, by using the following syntax :

module "example_team_ecr_credentials" {
  source    = "github.com/ministryofjustice/cloud-platform-terraform-ecr-credentials?ref=3.2"
  repo_name = "example-module"
  team_name = "example-team"
  # aws_region = "eu-west-2"     # This input is deprecated from version 3.2 of this module

  providers = {
    # Can be either "aws.london" or "aws.ireland"
    aws = "aws.london"
  }
}

3.1

• Built on 3.0
• Makes the account ID flexible (will adapt depending on your aws account)

KNOWN ISSUES :

• The provider being defined within the module, prevents the deletion of the module

Upgrading to 3.2 is recommended

3.0

This release contains a few changes :

• it encourage the use of the London region in AWS (eu-west-2)
• it uses the s3 path structure specific to our Live-1 bucket.

2.1

Life Cycle Policies

This release adds life cycle policy functionality.

By default, a life cycle policy is applied as a count of 40. Meaning and images after count 40 will be deleted.