ansible-clever - Ansible role for clever cloud deployment _ Forked from https://github.com/fretlink/ansible-clever

	Commit message (Collapse)	Author	Age	Files	Lines
*	deploy: try to restart the app when the CLI asks to do it	Paul Bonaud	2020-08-06	1	-2/+12
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In some cases (rollback or deployment errored on clever side), clever-tools will fail when calling `clever deploy` because it thinks the currently being deployed commit is already deployed. However in some cases the git pushed commit is not the currently running commit. Leading to a failure in our deployment process. The proposed solution from the clever tools error is to launch `clever restart`. Until we wait for https://github.com/CleverCloud/clever-tools/issues/422 to be fixed, let's do what the error message say: try to restart in case of a deployment failure.
*	fix(test): log all commads to `$binary-commands`	Clement Delafargue	2020-06-30	1	-1/+2
\| \| \| \| \|	Previously, only the commands not directly handled by the stub were logged. We want to log all commands instead
*	Make commit ids overridable in the script mock	Clement Delafargue	2020-06-30	1	-3/+6
\|
*	tests: expectations on binary stub	Paul Bonaud	2020-06-23	1	-0/+1
\|
*	deploy: remove custom polling script now that the CLI does it for us	Paul Bonaud	2020-06-17	1	-1/+1
\| \| \| \| \|	See recent changes (https://github.com/CleverCloud/clever-tools/pull/415) introduced in 2.5.0+ version of the clever cli tools
*	vars: fix `clever_base_env` by removing a variable if not necessary	Paul Bonaud	2020-03-24	1	-0/+14
	The `CC_RUN_COMMAND` variable was defined in case we use haskell binary as entrypoints. However if the `clever_haskell_entry_point` variable is not defined we shouldn't define the `CC_RUN_COMMAND` env variable.