Provide some standard module to dump this information on Yves as well as on Zed. This may be similar to, or perhaps included in the heartbeat page, but not only verbose in case of errors.
Do you need this config information for an environment (currently available in /config/Shared/config*-ENV-STORE.php files) or for specific (all) modules as well? Who should be able to see this data: everyone or only some users? There might be security issues (e.g. revealing a DB password) if access to this information is not restricted by ACL.
When do you usually need this info? What is the typical scenario when this info is required or requested?
Thank you.- Dmitriy
The typical situation (at least at the moment) is: after some observation was made i want to figure out (and make absolutely sure) which configuration is read by the application at a specific point in time. Doubts may arise from different configuration files setting the same values or the opcache not being refreshed correctly to name at least two. For us, a bare page dumping the configuration would be sufficient as it would be possible to guard these infrastructure-wise (using nginx, as we do for example to the git information already). All other scenarios (like using zed ui) make it assumably very hard to be applied e.g. on Yves.
But in general in would root for a more general solution to dump runtime information, as i wrote earlier. A Plugin-based solution like heartbeat, but not for error, but information gathering, could be very helpful, as it could solve more then one need - even some we are not aware of yet.
Thank you for clarifications. It definitely helps.
We plan to improve debugging functionality and will consider your idea. Let me update you when there is some news.
You won't be notified about changes to this idea.