New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass module.this.context to cloudposse/lb-s3-bucket/aws #86
Pass module.this.context to cloudposse/lb-s3-bucket/aws #86
Conversation
/test all |
1 similar comment
/test all |
@@ -57,6 +57,7 @@ module "access_logs" { | |||
noncurrent_version_transition_days = var.noncurrent_version_transition_days | |||
standard_transition_days = var.standard_transition_days | |||
force_destroy = var.alb_access_logs_s3_bucket_force_destroy | |||
context = module.this.context |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jwstric2 since you added the context
argument, can you remove the name
, namespace
, stage
, environment
, delimiter
, and tags
? context
will replace all those values so they're not needed. Obviously, let's keep attributes
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will do, I forgot to ask if those should be removed when opening up this PR.
…iter, and tags that are part of the given context
/test all |
I am unable to view the Infrastructure as Code analysis failure. If I should have access to view then I'm def willing to fix my authorization issues on my side and address the issue. |
/test all |
I'm not sure if these are new checks but don't seem to be coming from an area this PR touches. |
@nitrocode or @Gowiem, working with a gentleman on my team who suggested these be added as skips after talking to respective members through the slack channel, |
Some of these skips seem like they could be fixed with changes to the default vars; like the default ssl policy. Be happy if the team wants to track these in a separate issue/PR to evaluate |
that is correct, depending on the case we so |
/test all |
what
why
label_order = ["namespace", "environment", "name", "attributes"]
. The bucket being created was still using our defined stage of prod. In our use case, if the context is passed in, label_order will be respected by the lb-s3-bucket.