You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Henry Kuijpers (Jira)" <ji...@apache.org> on 2022/07/05 14:40:00 UTC

[jira] [Updated] (SLING-11437) CAConfig enable/disable Sling Feature Flags

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

Henry Kuijpers updated SLING-11437:
-----------------------------------
    Description: 
We have a default `ConfiguredFeature`, that we can configure through OSGi to enable or disable it. 

It would be nice to add an additional implementation of Feature, that could respect CAConfig values. This way, it would be possible to turn on/off a feature by specifying it in the configuration of the specific context it is configured in, as well as checked in.

It looks like the features already have the request available to be able to do those checks, using ConfigurationInjectResourceDetectionStrategyMultiplexer#detectResource to obtain the relevant resource (keeping in mind extensions that could use a different way of detecting the resource).

  was:
We have a default `ConfiguredFeature`, that we can configure through OSGi to enable or disable it. 

It would be nice to add an additional implementation of Feature, that could respect CAConfig values. This way, it would be possible to turn on/off a feature by specifying it in the configuration of the specific context it is configured in, as well as checked in.




> CAConfig enable/disable Sling Feature Flags
> -------------------------------------------
>
>                 Key: SLING-11437
>                 URL: https://issues.apache.org/jira/browse/SLING-11437
>             Project: Sling
>          Issue Type: New Feature
>          Components: Feature Flags
>    Affects Versions: Feature Flags 1.2.2
>            Reporter: Henry Kuijpers
>            Priority: Major
>
> We have a default `ConfiguredFeature`, that we can configure through OSGi to enable or disable it. 
> It would be nice to add an additional implementation of Feature, that could respect CAConfig values. This way, it would be possible to turn on/off a feature by specifying it in the configuration of the specific context it is configured in, as well as checked in.
> It looks like the features already have the request available to be able to do those checks, using ConfigurationInjectResourceDetectionStrategyMultiplexer#detectResource to obtain the relevant resource (keeping in mind extensions that could use a different way of detecting the resource).



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