Closed jmgreg31 closed 4 years ago
@schammah this build is passing. If you don't have any additional changes in mind for this release, I can merge.
One additional question. If the new proposed syntax is working to iterate through the cache behaviors, why not update for the origins, origin groups, member blocks...etc? Is there a reason you left those, i.e. certain conditions where the more involved iterator is needed?
example of legacy format in origin block:
dynamic "origin" {
for_each = [for i in var.dynamic_s3_origin_config : {
name = i.domain_name
id = i.origin_id
identity = lookup(i, "origin_access_identity", null)
path = lookup(i, "origin_path", null)
custom_header = lookup(i, "custom_header", null)
}]
yes i know, few things before we merge
provider.tf
do we really need it? i added versions.tf
and provider is more something you want to include in your implementation, should i git rm
it?@schammah sorry, wasn't clear to me what you were asking about the provider.tf
but I follow now. I removed it from the module. I added the provider as well create_cf
in the example
i think terraform output
will result empty unless you apply
before we merge wanna add a few more commits please
any chance i get rights to push to staging
branch?
i think
terraform output
will result empty unless you apply
You're right
before we merge wanna add a few more commits please any chance i get rights to push to
staging
branch?
The pattern I'd prefer to follow is submitting a PR to the staging branch instead of giving users access to push directly
@schammah Thanks for the work on this PR and appreciate you working through some of the CI processes.
I added additional_tags
and all the outputs to the example for more complete testing in the future. Merging this.
Testing @schammah changes