@@ -144,7 +144,8 @@ Deployment jobs also support _optional_ **hook scripts** from your project, loca
*`pre-ansible-playbook.sh` is executed **before** running `ansible-playbook` to perform specific environment pre-initialization such as generating a dynamic inventory,
*`post-ansible-playbook.sh` is executed **after** running `ansible-playbook` to perform specific environment post-initialization.
> :information_source: Your deployment (and cleanup) scripts have to be able to cope with various environments, each with different application names, exposed routes, settings, ...
> [!note]
> Your deployment (and cleanup) scripts have to be able to cope with various environments, each with different application names, exposed routes, settings, ...
> Part of this complexity can be handled by the lookup policies described above (ex: one script per env) and also by using available environment variables:
>
> 1. [deployment context variables](#deployment-context-variables) provided by the template:
@@ -182,7 +183,8 @@ The **static way** can be implemented simply by setting the appropriate configur
*`$ANSIBLE_ENVIRONMENT_URL` to define a default url pattern for all your envs,
*`$ANSIBLE_REVIEW_ENVIRONMENT_URL`, `$ANSIBLE_INTEG_ENVIRONMENT_URL`, `$ANSIBLE_STAGING_ENVIRONMENT_URL` and `$ANSIBLE_PROD_ENVIRONMENT_URL` to override the default.
> :information_source: Each of those variables support a **late variable expansion mechanism** with the `%{somevar}` syntax,
> [!note]
> Each of those variables support a **late variable expansion mechanism** with the `%{somevar}` syntax,
> allowing you to use any dynamically evaluated variables such as `${environment_name}`.
