System console configMgr is not accessible in higher environments

[aem-enthu27]

Hi ,

In AEM as a cloud service, system console configMgr access is not allowed, If this is the case then what is the point of OSGI configurations?

It is as goog as having constants rights? because we can not change the values directly from the console.

If I want to check any OSGI configuration values, How would I check ?

In my case I need to check 'Adobe Granite HTML Library Manager' OSGI configuration.

Thanks,

Ganesh

+91-9380201140

[Himanshu_Jain]

Check from developer console .

Ref : https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/develo...

[aem-enthu27]

Yes, we can check it from developer console but we can't change the values.

Then we can't call them as configurable anymore.

[Himanshu_Jain]

For every environment you have config interface available there you config the values 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/deploy...

[Jörg_Hoh]

You have read-only access to certain functionality via the Developer Console, but never write access. This is by design to avoid adhoc changes, which are almost impossible to trace.

If you want to change OSGI configuration, you have to deploy them via a run of pipeline.

[aem-enthu27]

What is the reason for blocking write operations ?

That means OSGI configurations are as good as constants right?

[Jörg_Hoh · Accepted solution]

OSGI settings always were deployment settings, and you should version-control them.

Runtime settings should be set in different ways, e.g. using Context Aware Configuration.