Erik Osterman (CEO @ Cloud Posse)

@mike-zipit > Document to initialize the git repo and do an initial commit to master Can you elaborate on what you're referring to?

Ultimately, we want to achieve DRYness, but with clarity on when to use what.

> I want to explore using docker file env parameters more, possibly with a more multi image layer approach. The biggest downside with this is needing to rebuild the image,...

@Mkrishna7 thanks for opening this issue. Yes, we need to update the documentation portal with links to the examples. Here are (3) complete examples: https://github.com/cloudposse/terraform-aws-jenkins/tree/master/examples

@alebabai use the `README.yaml` to generate this documentation.

@nitrocode is this still relative?

I agree - we should show how `atmos` augments terragrunt.

@nitrocode can you expand on the use-case? If using the command line arguments, would it generate a `component.yaml`?

We've implemented a workaround using GitHub Actions. Use https://github.com/cloudposse/github-action-atmos-affected-trigger-spacelift together with specially crafted policies to trigger only affected stacks based on comments in the PR. There's no way to fix...

We will solve this with `atmos clean all` see #272. I don't think this should happen automatically, or if it does, it would need to be a stack-level setting. It's...