| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
This reverts commit 85d1a7838d032ec7dfe858fce5dca3f5535199e4.
|
|
|
|
|
|
|
|
| |
In case a project already has a `.clever.json` file (for debugging
purpose to communicate with dev environment for instance) this step
was never done because of the `creates:`.
Removing it forces the role to always create a new clever.json file.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Updating to latest version of 1.1.1 helps to have a stable `clever
deploy` command.
This commit relies on the output of the command instead of manually
pooling the results with `clever activity` command.
|
|
|
|
| |
adding exports in the env file also quotes the variable values
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In ansible the `include_tasks` loads the tasks dynamically. Thus it
does not apply the tag specified at the include level to all sub
tasks.
In order to make sure all included tasks inherit the specified `tags:`
we need to include the tasks files "statically". It is very similar to
cases where we have a `when:` condition that we want to apply to all
included subtasks. cf https://docs.ansible.com/ansible/latest/user_guide/playbooks_conditionals.html#applying-when-to-roles-imports-and-includes
|
|
|
|
| |
This is a followup of #26
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
In some cases you might need to retrieve the ENV which is currently in
use by your clever application recently deployed.
If you specify a `clever_env_output_file` that is exactly what you
will get!
|
|
|
|
|
| |
This reverts commit 695ceaa28821660e17a1cf819cffebe1b5d8c7ca, reversing
changes made to 5485dbc4db3e141673457475bcda5fc88057739f.
|
|
|
|
|
| |
This reverts commit b17a839d622bdb36ddbe2e0667559c33e9b7fd8a, reversing
changes made to 695ceaa28821660e17a1cf819cffebe1b5d8c7ca.
|
| |
|
|
|
|
|
|
|
|
| |
Updating to latest version of 1.1.1 helps to have a stable `clever
deploy` command.
This commit relies on the output of the command instead of manually
pooling the results with `clever activity` command.
|
|
|
|
|
|
|
| |
Followup after the fix of #15 it was still missing another case of
"git" usage.
This should be the last fix about this variable 🤞.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Imagine such a usecase:
- project is in `/project`
- executing Ansible in `/ansible` with `clever_app_root: /project`
will fail deploying with the git push with the following error:
```
Not a git repository (or any of the parent directories): .git"
```
This PR fixes this.
|
|
|
|
|
| |
All variables "namespaced" with the role name is helpful to read
"client" configurations
|
|
|
|
|
|
|
|
| |
Every other variables are prefixed with `clever_` which makes the
definition of variables clearer from a "app" configuration point of
view.
WDYT?
|
|
|
|
|
|
|
|
| |
If your build tool only uses a shallow clone of your project, Clever
cloud will fail on first time git push. You need to git push a full
clone of your git repo for the first time deployment to clever.
This PR fixes that.
|
| |
|
|
|
|
|
|
|
|
| |
```
[DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using `result|failed` instead
use `result is failed`. This feature will be removed in version 2.9. Deprecation warnings can be
disabled by setting deprecation_warnings=False in ansible.cfg.
```
|
| |
|
|
|
|
| |
clever_app_tasks_file
|
| |
|
|
|