You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2016/11/07 10:47:58 UTC

[jira] [Updated] (SLING-6060) Context-Aware Config: Configuration property override providers

     [ https://issues.apache.org/jira/browse/SLING-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated SLING-6060:
------------------------------------
    Fix Version/s:     (was: Context-Aware Configuration Impl 1.1.0)
                       (was: Context-Aware Configuration SPI 1.1.0)
                   Context-Aware Configuration Impl 1.1.2
                   Context-Aware Configuration SPI 1.1.2

> Context-Aware Config: Configuration property override providers
> ---------------------------------------------------------------
>
>                 Key: SLING-6060
>                 URL: https://issues.apache.org/jira/browse/SLING-6060
>             Project: Sling
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Stefan Seifert
>            Priority: Minor
>              Labels: contextaware-config
>             Fix For: Context-Aware Configuration SPI 1.1.2, Context-Aware Configuration Impl 1.1.2
>
>
> add support similar to http://wcm.io/config/core/override-providers.html
> this is esp. useful for test/QA systems where a bunch of content and configuration packages are imported from the production system, and only a few of them need to be overwritten e.g. ip addresses, host names.
> these override providers should not be active by default. perhaps they should go into a separate package - but we need the SPI for them in the core implementation.
> this is somewhat related to SLING-6058
> information about overriding that is in place should be provided in the Configuration Management API (ConfigurationManager) as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)