Open k-brooks opened 3 years ago
That's a big problem when you use Ansible as an exemple... Ansible with SSM connection plugin can update system wide env vars like the PATH, but in fact any SSM session (including next Ansible tasks) are always using the ENV context from the SSM service start
Chef has a similar problem
We have a use case whereby (system) environment variables are created in one session managed by the ssm-agent, and consumed in another, later on. We have found that unless we restart the agent, the environment variables are not available in later sessions through the (session) environment provided by the agent. It would be great if we could trigger an environment variable reload or something of the like to permit environment variable use across sessions.