| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
| |
clever_app_tasks_file
|
| |
|
