Erik Osterman (CEO @ Cloud Posse)

@Cerebrovinny thanks for the screenshot. Looks like we're not following the general UA convention. Let's change to: `Atmos/1.181 (Cloud Posse; +https://atmos.tools)` For reference, see: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent

@milldr make sure look and feel reflects the other list commands. Also, I think @Cerebrovinny created an interface so we get the same behavior, look, and feel to atmos list...

@Cerebrovinny note the tests failed for `Tests / [mock] demo-vendoring (pull_request)` ``` Processing vendor config file 'vendor.yaml' either 'spec.sources' or 'spec.imports' (or both) must be defined in the vendor config...

Technically, this is already supported. As you can see [here](https://github.com/gruntwork-io/git-xargs/blob/070d1a68d080aee71cba6ae43c3eb0f5bf8af3c5/repository/repo-operations.go#L38) it's just calling `ioutil.TempDir` which properly handles temp dir environment variables. (In my experience, most syscalls to get temporary directories...

Aha, my fault - I didn't catch that.

Add a list of anti-patterns - Do not use `` tags for formatting. Instead propose changes to the CSS. - Do not use chapter headings (e.g. `### term`) for definitions,...

We're investing some more in AWS Config soon. This might come up. We're adding support for Organizationl Conformance Packs soon. @aknysh do you know more about the custom rules?

I suspect there's a possible cycle in your stack configuration leading to an infinite loop. This happens by having circular references using templating functions like `atmos.Component`

I can see how this would be helpful. Since we already support generation of other sections of the `terraform { ... }` block like the `backend`, this would be easy...

This sounds like a great enhancement, however, this has not yet been prioritized or scheduled. No ETA.