The SLC deployer infers the storage backend by looking at what parameters are passed. Giving it all config elements that can be found in the configuration store bears a risk of confusing the SLC deployer about which backend to use. This can be the case if the user is switching between two databases, for instance, SaaS and DockerDB. In this scenario, all configuration elements will be present in the store.
The SLC deployer infers the storage backend by looking at what parameters are passed. Giving it all config elements that can be found in the configuration store bears a risk of confusing the SLC deployer about which backend to use. This can be the case if the user is switching between two databases, for instance, SaaS and DockerDB. In this scenario, all configuration elements will be present in the store.