BBL-563 addons moved to their own layer

What?

Addons were moved to their own layer.

Why?

To avoid cyclical redundancies between cluster and identities layers.

This way all the EKS layer can be applied as:

# cd into the EKS layer
echo "vpc_enable_nat_gateway = true" >  network/terraform.auto.tfvars
leverage tf apply --layers network
# If this is the first time you apply `network` layer:
#     set the VPC peerings from `shared` account and 
#     add the cluster VPC CIDR to the VPN server
# Connect to the VPN
leverage tf apply --layers cluster,identities,addons,k8s-components

... and for destroying it:

# cd into the EKS layer
leverage tf destroy --layers k8s-components,addons,identities,cluster
echo "vpc_enable_nat_gateway = false" >  network/terraform.auto.tfvars
leverage tf apply --layers network

References

Infracost report

💰 Monthly cost will not change

Cost details

``` ────────────────────────────────── Project: binbashar/le-tf-infra-aws/apps-devstg/us-east-1/databases-aurora/rds-export-to-s3 Module path: apps-devstg/us-east-1/databases-aurora/rds-export-to-s3 Errors: Passed var file does not exist: apps-devstg/us-east-1/config/backend.tfvars. Make sure you are passing the var file path relative to the --path flag. Diff baseline error: Passed var file does not exist: apps-devstg/us-east-1/config/backend.tfvars. Make sure you are passing the var file path relative to the --path flag. ────────────────────────────────── Project: binbashar/le-tf-infra-aws/apps-devstg/us-east-1/databases-mysql --/rds-export-to-s3 Module path: apps-devstg/us-east-1/databases-mysql --/rds-export-to-s3 Errors: Passed var file does not exist: apps-devstg/us-east-1/config/backend.tfvars. Make sure you are passing the var file path relative to the --path flag. Diff baseline error: Passed var file does not exist: apps-devstg/us-east-1/config/backend.tfvars. Make sure you are passing the var file path relative to the --path flag. ────────────────────────────────── 2543 cloud resources were detected: ∙ 595 were estimated, 456 of which include usage-based costs, see https://infracost.io/usage-file ∙ 1789 were free, rerun with --show-skipped to see details ∙ 159 are not supported yet, rerun with --show-skipped to see details ```

_{This comment will be updated when code changes.}

binbashar / le-tf-infra-aws