[
https://issues.apache.org/jira/browse/SLING-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876212#comment-16876212
]
Henry Kuijpers commented on SLING-8548:
---------------------------------------
Agree, but that leaves you only with the option to override it. Not remove it
completely.
I.e. ACS AEM Commons BundleDisabler:
* install.author -> disable 2 bundles
* install.author.local -> disable 0 bundles
But it's not possible, in this case, to not have the BundleDisabler config for
runmode local.
In this case, the BundleDisabler is also exactly why I wanted to do this: It
now yields a "0 bundles, consider removing this config" message everytime it
starts. It would be much nicer if I could avoid having *any* config at all for
it, for local.
> Allow specifying negative runmode match
> ---------------------------------------
>
> Key: SLING-8548
> URL: https://issues.apache.org/jira/browse/SLING-8548
> Project: Sling
> Issue Type: New Feature
> Components: Installer, JCR
> Affects Versions: JCR Installer 3.1.26
> Reporter: Henry Kuijpers
> Priority: Major
>
> Currently, runmodes can be specified as the name of the "config" or "install"
> folders. I.e. "config.author" or "install.dev".
> We often see the use-case where we want to do a configuration for every
> environment, except one (most often "local").
> It would be nice if we can do something about the configuration syntax to be
> able to specify a negative match, i.e.:
> * install.author.!local
> * install.author.local
> Instead of:
> * install.author.local
> * install.author.dev
> * install.author.test
> * install.author.acp
> * install.author.prod
> This way, we do not have to duplicate our configurations 3 times. :)
> Any thoughts on this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
