Erik Osterman (CEO @ Cloud Posse)
Erik Osterman (CEO @ Cloud Posse)
Use case: https://github.com/cloudposse/terraform-aws-eks-cluster/blob/bef1d418eff61ed8257f36554abd9026166ee62a/auth.tf#L49-L60 See: https://github.com/hashicorp/terraform-provider-http/issues/49
First off, this is sweet! We are looking for a way to vendor terraform modules and this looks like it could be the best way. It’s clear to me how...
## what * Convert `README.md` to our `README.yaml` syntax ## why * Consistency
## what * Convert `README.md` to `README.yaml` ## why * So we can better integrate with all of our other repos * Consistency
We came across `policy-bot` and eagerly deployed it without realizing we couldn't do what we had hoped to do. We run a large [Open Source GitHub organization](https://github.com/cloudposse) with hundreds of...
## what - Update readme.md ## why - Latest copy
## what - Reran `make readme` to rebuild `README.md` from `README.yaml` - Migrate to square badges - Add scaffolding for Settings, Renovate, Dependabot, and Mergify ## why - Upstream template...
## what - Add terminal configuration instructions - Add installation instructions for fonts ## why - Not everyone is familiar with what makes atmos TUI look good =)
Be able to use atmos without understanding stack name conventions, and be prompted to select stack names. ``` atmos terraform plan vpc ``` Would provide a multi-selector to select that...
## what * Emit a warning to STDERR that an out-of-date version of atmos is in use * Support a `atmos.yaml` configuration setting to specify a list acceptable semver ranges...