-
-
Notifications
You must be signed in to change notification settings - Fork 767
Description
This was discussed for several times and was an issue more than a few times internally and in #community as well.
Infrastructure as a code is cool if you control the entire code, but StackStorm exchange has packs with Sensors, Rules, Aliases which are enabled by default. This brings a lot of noise after installing a pack.
The worst, - when we change the sensor locally to enabled: false
, next pack re-installation or re-provision replaces that change and st2ctl reload brings sensor or whatever back online.
Same problem is when vice-versa content is disabled by default in Exchange Pack and we want to enable it in our system.
The proposal is to have a mechanism to optionally blacklist/whitelist Sensors, Rules, Aliases via pack config which will take precedence over the metadata with possibility to include/exclude specific content to be registered or disabled with enable-many, disable-many, enable-one, disable-one, glob logic.
This way we could keep infrastructure as a code via existing /opt/stackstorm/packs/<pack>.yml
definition.
This will solve #3016 and help with #3963 as well as other issues related to pack content registration.