| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|\
| |
| | |
don't run `clever deploy` if the app is up-to-date
|
| |
| |
| |
| |
| |
| | |
`grep -v` makes sure a file contains other lines than the one that
matched. This is different from `! grep` which makes sure the file
does not contain a line that matched.
|
| |
| |
| |
| |
| | |
Previously, only the commands not directly handled by the stub were
logged. We want to log all commands instead
|
| |
| |
| |
| |
| | |
It makes sure `clever deploy` is _not_ called if the application
is up-to-date on clever cloud
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
Running `git push` when the remote is up-to-date
no-ops (it does not trigger a deployment, but it does not fail either).
Running `clever deploy` when the remote is up-to-date triggers a failure. Here, we care about the _end result_ (ie the app is deployed on the correct commit), so no-oping is more appropriate.
This behaviour is not baked in `clever-tools`, but I think it should. I opened an issue. This script
is a temporary workaround. (at least I hope it's temporary)
https://github.com/CleverCloud/clever-tools/issues/422
|
|\
| |
| | |
fix: prevent crash when the deployment times out
|
| |
| |
| |
| |
| |
| | |
NIX_PATH used to be enough to select the channel to use, but as Travis
add the nixpkgs-unstable channel we can get unexpected results when
nix decides to push a new unstable version out there in the public.
|
|/ |
|
|\
| |
| | |
dhall: add missing configuration for clever_restart_only variable
|
|/
|
|
| |
This change was forgotten in #70
|
|\
| |
| | |
feature: add a new 'clever_restart_only' flag to restart an app
|
| | |
|
| | |
|
|/
|
|
|
| |
This new flag will perform a restart on the target clever cloud
application instead of deploying it.
|
|\
| |
| | |
core: README cleanup and test env cleanup
|
| | |
|
|/
|
|
| |
Part of #66
|
|\
| |
| | |
scalability configuration
|
| |
| |
| |
| | |
They make sure that ansible does not crash while calling `clever scale`
|
|/
|
|
| |
Closes #52
|
|\
| |
| | |
fix: make sure not to include unecessary ENV variable
|
| |
| |
| |
| |
| |
| |
| | |
This is a fix to an unfortunate bug introduced by #64 because we had a
default value set to `None` on the
`clever_haskell_entry_point`. Ansible considers `None` as a defined
value so the `is defined` condition doesn't match our need
|
| | |
|
|/ |
|
|\
| |
| | |
Add optional build flavor configuration
|
| |
| |
| | |
Co-authored-by: paulrbr-fl <43074087+paulrbr-fl@users.noreply.github.com>
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Use JSON import for environment variables
|
| | |
|
|/
|
|
|
|
|
|
| |
The env can be provided as a JSON list `[{"name": "PORT", "value": "8080"}]`.
The `dict2items` filter provided by ansible is _almost_ what we want, but it
keeps the value original types (a boolean is kept as a boolean in the JSON value).
Since environment variables are strings and `clever-tools` does not want to make
the implicit coercion for us, we need to do it ourselves.
|
|\
| |
| | |
deploy: remove custom polling script now that the CLI does it for us
|
|/
|
|
|
| |
See recent changes (https://github.com/CleverCloud/clever-tools/pull/415)
introduced in 2.5.0+ version of the clever cli tools
|
|\
| |
| | |
fix: there was a bug in the generate env file
|
|/
|
|
|
| |
Bug Introduced by #57 because the `to_json` filter quotes the given
value if it's a string, so the PR was "double quoting" each values.
|
|\
| |
| | |
fix `clever_base_env` by removing a variable if not necessary
|
|/
|
|
|
|
| |
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.
|
|\
| |
| | |
config(dhall): adding redis and mysql addon types
|
|/ |
|
|\
| |
| | |
Quote env vars to support multiline values
|
|/
|
|
|
|
|
|
|
| |
clever-tools now supports multiline env vars. It did so by supporting
quotes in the formats it reads from.
This commit quotes the exported values using the `tojson` filter.
Of course, a better solution would be for clever env to directly read
json value, but it's not there yet
|
|\
| |
| | |
ci: fix nix version and nix channel version
|
|/
|
|
|
|
|
| |
In order to avoid having bad surprises with automatic updates let's
fix the nix channel version. For now the default travis behavior is to
use `nixpkgs-unstable` (see
https://docs.travis-ci.com/user/languages/nix#overview).
|
|\
| |
| | |
fix: addon environment variables fetch for clever >= 1.5.0
|
|/
|
|
|
|
|
|
|
| |
It seems the output of `clever env` has changed and now env values are
surrounded by quotes with the latest 1.5.0 clever tools version.
We used to add quotes ourselves because they were missing in the
output. So this commit is adapting its parsing depending of the clever
tools' version.
|