I don't ever see us moving a provider back behind a feature flag after we
move it out from one, but I agree with the point. If a user was using a
devel version and in a release, we moved a provider behind a flag, they
would stop working and their bootstrapped environment would be stuck
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-04-23 12:27 AM, John Meinel wrote:
Thinking it through a bit more, I wonder if that is the best
option. Because if someone is already bootstrapped on CloudSigma
you really don't have any reason for it to not support CloudSigma.
It is just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-04-22 09:00 AM, Wayne Witzel wrote:
I've been told to place cloudsigma provider behind a feature flag,
but the result of that is that the provider is not registered
unless the env variable for cloudsigma is set.
So after wrapping
I've been told to place cloudsigma provider behind a feature flag, but the
result of that is that the provider is not registered unless the env
variable for cloudsigma is set.
So after wrapping the registration of the provider in the feature flag
(see:
https://github.com/juju/juju/commit
cloudsigma provider behind a feature flag,
but the result of that is that the provider is not registered
unless the env variable for cloudsigma is set.
So after wrapping the registration of the provider in the feature
flag (see:
https://github.com/juju/juju/commit
