RB
There is an input in the upstream module https://github.com/cloudposse/terraform-aws-codebuild#input_badge_enabled Would you like to contribute this change ? We're always looking for contributors 😄 https://github.com/cloudposse/terraform-aws-cicd/blob/81c4e109751dadf1d9cefb5341503a85f11dfbdf/main.tf#L205
Yep, I meant if a github release is marked as a `pre-release` versus the semver equivalent.
Yep you're right. From ecs codepipeline, there is a separate codepipeline resource that gets created. https://github.com/cloudposse/terraform-aws-ecs-codepipeline/blob/13332037cb896137ae6dc09f3efa823c48300bc2/main.tf#L355 Instead of having two hard resources in both modules, it would be good to...
goreleaser is nice here is a nice GitHub action that uses it https://github.com/cloudposse/atmos/blob/master/.github/workflows/build.yml
The create_before_destroy lifecycle sounds like it could cause other problems. I'll defer to my teammates to see if they have any issues with it. cc: @aknysh @jamengual
Hi @benmotyka. Thank you for the contribution. We currently have an s3 bucket module that has been updated to our latest standards, just like our security group module. We're hoping...
As a workaround, a tool like [json2hcl](https://github.com/kvz/json2hcl) could be used to convert the json to hcl, then run `tfupdate`, and convert back using the dame tool
Seems like this has been implemented by a separate tool https://github.com/keilerkonzept/terraform-module-versions
Hi @fcojfernandez @res0nance @MRamonLeon What are some of the thoughts on this ?