Generate "Configuration parameters" documentation page automatically, to avoid mismatches between documentation and code

[rdimaio]

The "Configuration parameters" docs page describes various configuration parameters across Rucio.

From what I can see, this documentation page is maintained manually. The issue with this is that some configuration parameters might change in the code (e.g. default values could be modified), and the documentation might become outdated.

It would be ideal to automatically generate this documentation from the code containing the configuration parameters themselves, in order to keep them in sync.

This would prevent issues like this (rucio/rucio#5965) from occurring.

[rdimaio]

Related: #183 (as it also pertains documentation about config)

[voetberg]

So I spent some time looking into this, and grabbing the defaults from the config file is easy enough with the MDX format introduced by docusaurus3, but the question becomes - What defaults are being used where? Is grabbing the default config file from /opt/rucio/rucio.cfg enough?

[rdimaio]

So I spent some time looking into this, and grabbing the defaults from the config file is easy enough with the MDX format introduced by docusaurus3, but the question becomes - What defaults are being used where? Is grabbing the default config file from /opt/rucio/rucio.cfg enough?

Good question, I assume the defaults used in rucio.cfg are the ones we should use here, but I'm not sure. @bari12 ?