Open plopidou opened 3 years ago
Hi any news on this? It feels very weird that %% env variables work under individual [program] sections and yet not under the global [supervisord] section. Being able to use that under [supervisord] would help keeping some configuration files being more DRY.
Thanks!
Hello,
Tick the appropriate box:
[ ] The example provided is full of bugs [ ] There is actually an issue, but we haven't had the time to look at it
Thank you :)
Hi,
Not sure if this is a bug or I am not setting things up correctly.
Imagine the following (snipped) /etc/supervisord.conf file:
DYNAMIC_VAR
contains two "%s" placeholders, supposed to be replaced at runtime in a way similar to this:... thus resulting in
bar_foo_bar
.Now when I declare
DYNAMIC_VAR
in /etc/supervisord.conf, supervisord cannot start, and complains:Please note: . that environment variables with only one escaped
%s
work fine. . that moving the "double %s" variable to individual included files (for individual programs) seems to work fine. For example:I am (I think!) following the docs, but could there be an issue with the presence of multiple escaped % within the same environment variable, only when declared in the top-leve configuration files?
Many thanks!
edit: supervisor 3.4.0 on Centos7.9.