Command line option to list active config parameters

[mmattel]

Is your feature request related to a problem? Please describe.

Identified when documenting ocis config.

When reading the dev docs about the configuration arithemtics, you get a clear warning that if you do not take very much care, a misconfiguration can sneak in resulting in a different behaviour than expected. This can happen because of the way a final configuration gets assembled (the configuration arithmetics) out of different yaml files. The issue is, that you have a bunch of yaml files, but currently you cant tell how the final assembled configuration looks like.

Describe the solution you'd like

Have a command line option when calling ocis like --print-config which prints the final assembled and active configuration. It would be beneficial if such a print out is seperated by comments based on which extension it belongs.

Describe alternatives you've considered

There is no alternative.

Additional context

Points to be considered:

1. This is benificial when you want to review your final config AND
   you can export the config for testing purposes
2. Any secret parameters need to stay secret - like we do in classic server when printing the config
3. Needs documentation in dev docs and in docs-ocis

Note, please file a docs-ocis issue when this gets implemented so we can update the documentation accordingly.

@butonic @wkloucek @dragonchaser (as discussed) @micbar @pmaier1
@EParzefall fyi

[wkloucek]

see also #2672

[dragonchaser]

Ok #3646 is a duplicate, it would be nice to take over the auto redaction I described there.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

[mmattel]

dont close

[mmattel]

bot, reopen

[d7oc]

@micbar @kobergj Would it be possible to include this? This feature would have same us some time in today's debugging session as this would have shows directly that the policies service has not correctly read his config part.

[wkloucek]

@micbar @kobergj Would it be possible to include this? This feature would have same us some time in today's debugging session as this would have shows directly that the policies service has not correctly read his config part.

The "proxy" service already has a config report http endpoint. Others are not implementing it.

[mmattel]

The "proxy" service already has a config report http endpoint. Others are not implementing it.

Means we have some action points:

• Implement the config report http endpoint in all services where missing.
• Add this task to the "new service" documentation in owncloud.dev.
• Per service documentation in the readme's.

[wkloucek]

The "proxy" service already has a config report http endpoint. Others are not implementing it.

Means we have some action points:

• Implement the config report http endpoint in all services where missing.
• Add this task to the "new service" documentation in owncloud.dev.
• Per service documentation in the readme's.

Don't know if it was agreed that this http endpoint on the debug server of the proxy is the way to go for all other services. I think this was more of a POC.