a72d3c83cf
The existing comment about `set -e` appears to no longer apply. I've been deploying clusters while iterating on these changes, hitting many "Bootstrap failure" states. I have reliably been able to find stdout.log.gz containing the relevant failure message for these failed clusters. There were a few commands failing for every cluster, so I had to make some small cleanup changes in order for bootstrap to complete with the new `set -eo pipefail` setting. |
||
|---|---|---|
| .. | ||
| envs | ||
| files | ||
| inventory | ||
| deploy.yml | ||
| render_and_copy_to_s3.yml | ||