Instead of using a jinja-template which is fed with env variables,
add a python script which can merge multiple config sources (files, or env)
into a combined rucio.cfg.
By default, the behavior is almost unchanged. Only difference: Env variables
which were not referenced in the jinja template but were set by kubernetes
will now be merged into the config (were ignored before).
Example, on atlas deployment, the following additional config values will appear
[core]
default_mail_from = ...
geoip_licence_key = ...
which are set in flux, but not referenced in the rucio.cfg.j2
Instead of using a jinja-template which is fed with env variables, add a python script which can merge multiple config sources (files, or env) into a combined rucio.cfg.
By default, the behavior is almost unchanged. Only difference: Env variables which were not referenced in the jinja template but were set by kubernetes will now be merged into the config (were ignored before). Example, on atlas deployment, the following additional config values will appear [core] default_mail_from = ... geoip_licence_key = ... which are set in flux, but not referenced in the rucio.cfg.j2