Releases: palantir/bouncer
0.6.16
Remove failure if new unhealthy nodes exist on start (#20)
It's happened to me fairly often that a TF apply has timed-out because a node was unhealthy for some external reason. I fix the external reason, and just want bouncer to continue waiting for the new instance to come up and then continue. However, currently, it bails out immediately when you start it in the fashion, so I have to wait for that one instance to become healthy, and only then kick-off the TF apply to re-run.
I'm not sure why we need this precondition, as without it, bouncer will just immediately start-up in a "waiting for instance to become healthy" state, which seems just fine.
Excavator: Update godel to latest version (#19)
Excavator: Update godel to latest version (#18)
Excavator: Update godel to latest version (#17)
Excavator: Update godel to latest version (#16)
Excavator: Update godel to latest version (#15)
0.6.15
Fix sha256sum path
Since godel2 changed the path of created dists.
0.6.14
Fix godelw publish param
0.6.13
Stop vendoring yourself
Update godel to latest version on GitHub.com repositories
0.6.12
0.6.11
Use correct env var (#7)
As per https://docs.aws.amazon.com/cli/latest/userguide/cli-environment.html
Fixes #6
Listing permissions required to run the bouncer. (#8)
Only warn if ASG size is 0 (#9)
Maybe for bootstrapping, you want to set an ASG desired capacity to 0, so changing bouncer to just warn you in this case instead of exiting with error.
0.6.10
Better download on README
Cross-compile for all envs that hashicorp does
Except Solaris which is having some issues.
Switch to go's official docker image
Document published release location
0.6.9
Fix-up sha256sum printing
Godel rebuilds every run, so no reason to cache build/ or dist/ after all. Print SHA256Sum to get the actual sum that was published - I can use this to plugin to homebrew