Erik Osterman (CEO @ Cloud Posse)

We should overhaul https://atmos.tools/cli/configuration and improve the documentation of all fields.

Here are some examples of charts: - Maintained by cloudposse: https://github.com/cloudposse/charts/tree/master/incubator - 100s are maintained by community: https://github.com/helm/charts

Waiting for more feedback on how we can generate pull secrets dynamically for unlimited staging environments

Colors should probably be different and size too.

Let's hold off on this one. I think it will look too ugly. Haha.

We've recently extended atmos to support all types of datasources, although most are from `gomplate`. Unfortunately `gomplate` [doesn't provide native SOPS](https://github.com/hairyhenderson/gomplate/issues/869). It's a really interesting idea if stack configs could...

We can include them simply in the Atmos core, without requiring them in the upstream dependencies. Also, if any of your team would be interested in getting more involved hands-on,...

I agree - there should be some baseline `atmos.yaml` either compiled into `atmos` or downloadable.

A tangentially related feature has been been introduced in #529, which adds a default `atmos.yml` config, if none is found. This is a stepping stone to implementing the above.

I like the option. And if it's scary, then default to a prompt =) Geodesic should be self-contained, and explaining other commands like calling `docker` directly should be avoided and...