add a default rucio config in clients. #267

[rcarpa]

The jinja file was fallbacking to a default config, so this was a regression to completely remove it.

[garciagenrique]

I was too slow testing things 😅 . I confirm that everything works fine now. Building the image locally and setting up all the env vars (just for testing) in the pod manifest results in the following;

<<K9s-Shell>> Pod: rucio-dev/rucio-client-dev-test-local | Container: rucio-client-dev-test-local 
File rucio.cfg not found. It will generate one.
INFO:root:Merged 16 configuration values from /opt/user/rucio.default.cfg
INFO:root:Merged 19 configuration values from ENV
Enable shell completion on the rucio commands
[user@rucio-client-dev-test-local ~]$ cat /opt/rucio/etc/rucio.cfg 
[client]
rucio_host = https://vre-dev-rucio.cern.ch
auth_host = https://vre-dev-auth-rucio.cern.ch
ca_cert = /etc/pki/tls/certs/CERN-bundle.pem
auth_type = userpass
username = <USENAME>
password = <PASSWORD>
account = root
client_cert = /opt/rucio/etc/usercert.pem
client_key = /opt/rucio/etc/userkey.pem
client_x509_proxy = 
request_retries = 3
x509_proxy = /tmp/x509up_u0
vo = escape

[policy]
permission = escape
schema = escape
lfn2pfn_algorithm_default = hash
support = https://github.com/rucio/rucio/issues/
support_rucio = https://github.com/rucio/rucio/issues/
package = escape

[common]
multi_vo = test_value

[user@rucio-client-dev-test-local ~]$ 

Thanks @rcarpa !!

[rcarpa]

Thank you for testing. It will be built and released via the normal build mechanism at next rucio release. However, if it's impactful for your production operation, please inform us. We can arrange a patch release outside the normal release cycle.

[garciagenrique]

Absolutely not ! We can wait for the next release without problems !