From 567977285542274d3fef0fd3df556e5f9bbc1f79 Mon Sep 17 00:00:00 2001 From: Paul Bonaud Date: Fri, 30 Nov 2018 15:57:33 +0100 Subject: feat(post_deploy): Add a post deploy task to fetch deployed env 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! --- README.md | 1 + 1 file changed, 1 insertion(+) (limited to 'README.md') diff --git a/README.md b/README.md index b932c7f..f156f5c 100644 --- a/README.md +++ b/README.md @@ -31,6 +31,7 @@ Variables for the application - `clever_syslog_server`: UDP Syslog server to be used as UDPSyslog drain for the application, optional. Example: `udp://198.51.100.51:12345`. - _Obsolete_: `syslog_server`: Same as above but was replaced by `clever_syslog_server` since v1.5 of this role. - `clever_metrics`: a boolean to enable or disable metrics support. Optional, default to `true`. +- `clever_env_output_file`: as a post deploy task you might need to retrieve the full Clever environment configuration (i.e. with addon env variables). If this variable is set to a filename then the env will be retrieved after a successful deploy inside this file. Optional. Variables specific to deployment, default should be fine: - `clever_cli_version`: Version of clever cli tools, default to `0.9.3`. -- cgit v1.2.3