Erik Osterman (CEO @ Cloud Posse)

Please check the test failures.

Thanks for the quick fix! I haven't had a chance to test it yet. It does look like there are others. The ones I noticed were also missing are "resource_file"...

Could you clarify if you're strictly referring to using TFC as a state backend or TFC also as a GitOps platform?

There are a few options. ## option 1 Use an ACM certificate provisioned with terraform and associated with the `nginx-ingress`. https://github.com/cloudposse/terraform-aws-acm-request-certificate Reference implementation here: https://github.com/cloudposse/terraform-root-modules/tree/master/aws/acm Then set the ingress annotations...

Example: https://dev.jlelse.de/back-to-static-using-hugo-to-easily-build-static-websites/

https://github.com/cloudposse/docs/pull/59

The last time this happened, it was due to `PrometheusOperator` having insufficient memory. We were turned on to this fact as a result of another alert firing that the pod...

Maybe we should add this to our `README.md` template and automatically generate it.

# Managing Secrets Use `chamber` with [terraform-aws-iam-chamber-user](https://github.com/cloudposse/terraform-aws-iam-chamber-user) # Naming Kubernetes Contexts Use cluster name. e.g. `us-west-2-staing-cloudposse-co` # Use a `codefresh.yml` build file Always include the pipeline manifest in the source...

https://github.com/cloudposse/docs/pull/129/