We have built our app to be configurable via OSGi configurations, which is th AEM way.
This works great locally against the cloud SDK.
However, when we deploy to the cloud, the configMgr seems to be blocked. This means we cant edit any of the critical run time variables, such as timeouts, switching features on off etc.
This is a huge problem. It would mean we have to re-write our services to read config from pages of the CMS or similar, which is a significant re-write.
Is there any work around to being able to view and edit our OSGi configs at runtime?
Adobe MUST remove these features from the cloudSDK if they are not available on any cloud env, otherwise we are developing for a completely different system. this also includes the excellent i18n translation system, which is now removed on the cloud, but is still present in the SDK. This also required a significant rewrite, and is a very poor solution now.
