[jira] [Created] (FELIX-6730) Web Console configurations page does not take into account ConfigAdmin plugins

["Robert Munteanu (Jira)" <ji...@apache.org>]

Robert Munteanu created FELIX-6730:
--------------------------------------

             Summary: Web Console configurations page does not  take into account ConfigAdmin plugins
                 Key: FELIX-6730
                 URL: https://issues.apache.org/jira/browse/FELIX-6730
             Project: Felix
          Issue Type: Bug
          Components: Web Console
    Affects Versions: webconsole-5.0.8
            Reporter: Robert Munteanu
         Attachments: image-2024-10-10-11-00-01-441.png, image-2024-10-10-11-03-32-255.png

I am using the {{org.apache.felix.configadmin.plugin.interpolation}} plug-in for processing placeholders in configuration and when I do that the Configuration view from [http://localhost:8080/system/console/configMgr] does not take into account the changes applied by the plugin-in.

Here's what I did:

1. Defined OSGi config for a (declarative services) component that uses placeholders. Web console status config shows it as
{noformat}
PID = org.apache.sling.engine.impl.SlingMainServlet
  sling.includes.checkcontenttype = $[env:INCLUDES_CHECK_CONTENT_TYPE;type=Boolean;default=false]
{noformat}

2. Launched my app with the env var INCLUDES_CHECK_CONTENT_TYPE set to true

3. Checked the configurations tab and noticed that the value is confirmed to be non-default but false

!image-2024-10-10-11-00-01-441.png!

This is very confusing in case of boolean values. In case of strings you would see the placeholder and somehow figure out what is going on, but here it's basically impossible.

4. We eventually figured out by going to either the services tab or the components tab that the properties had the right value but it took a lot of time

 !image-2024-10-10-11-03-32-255.png! 

I think it would be great if the configurations view would be able to show the processed configuration properties, maybe alongside the 'raw' ones, as it would make it much easier to understand what the effective property value is.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)