Secrets.yaml hiearchy

Configuration
1

I have some secrets that should be grouped so instead of

somelongname_client_password: xxx
somglongname_client_key: yyy

I would like to setup the secrets file as:

somelongname:
  client_password: xxx
  client_key: yyy

which would also make it clearer what secrets belonged to.

I did try !secret somelongname.client_password but this doesn’t work.

So does secrets.yaml have to be flat with all entries at the root level?

2

Yes it has to be a flat file.

3

You can add comments to make it clearer.

##some long name details
sln_client_password: xxx
sln_client_key: yyy

With most details like this now being provided through the UI rather than the config your secrets file won’t contain as many secrets as you’d expect