Closed
Conversation
…ty_group_[ingress|egress]_rule resource
…examples dir breaks things
Closed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes:
Additions:
Nametags to Security Group Rules. These match thedescription.logs_s3_bucket, the boolenable_access_logsandenable_connection_logs(both default tofalse) need to be set totrueto enable logging of either type.alb_ssl_policytoELBSecurityPolicy-TLS13-1-2-2021-06.enable_waf_fail_openwith a default value offalse.preserve_host_headervariable with a default value offalse.drop_invalid_host_headersvariable with default value oftrue.BREAKING CHANGES:
aws_security_group_ruleresources for both ingress and egress rules withaws_vpc_security_group_ingress_ruleandaws_vpc_security_group_egress_rule.~> 5.0.${var.name}-${var.environment}to${var.environment}-${var.name}.alb/${var.name}-${var.environment}for access logs is nowalb/${var.environment}-${var.name}. This prefix is shared by both` access and connection logs.alb_certificate_arnstoalb_listener_certificate_arns.ecs-${var.name}-${var.environment}-HTTPSto${var.environment}-${var.name}-ecs-HTTPS.General Housekeeping
terraform-docs).pre-commit-config.yamlbecause it is not possible to ignore theexamplesdirectory. So a targetcheckhas been added to theMakefile.check-jsonschemapre-commit for.pre-commit-config.yaml,.markdownlint.ymlandrenovatealong withgithub-workflows(which is their name for Actions).terraform-docs-systemwhich has an expectation thatterraform-docsis installed locally. This also uses the official GitHub Action but there is a bug. So across the org, I've tried to find the right configuration adopting the official action along with pre-commit-hook and making it work eveywhere. I believe this combination works.terraform-docswill still continue to work locally, but in GitHub Actions, we pass an Env Var ofSKIP=terraform-system-goto not callterraform-docsa second time via pre-commit.