Can the operator be configure to controlled which stacks are allowed to deploy

[csantanapr]

Feature Request

Is your feature request related to a problem?

Can I configure the operator to only allow a set of stacks to be deploy? I see constants and defaults, but what about if I only want to allow a small set of stacks to be deploy any other stacks to just be ignored and not deployed. I'm looking at the sections of the docs https://github.com/appsody/appsody-operator/blob/master/doc/user-guide.md#operator-configuration

Describe the solution you'd like

Not sure what would be the optimal solution.

[leochr]

@csantanapr The operator currently doesn't limit the deployment based on stacks. Stack is an optional field. We'll give some thought to this requirement. One option is to have allowedStacks and/or ignoreStacks in the constants map and to check that before deployment.

[arthurdm]

My view is that such control is done at the "hub" level, as Champ controls which stacks / collections are active. I think the appsody operator shouldn't have this config, otherwise we create synchronization issues with the rest of the framework.