-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 the
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:
# juju-core 1.23.1
A new proposed stable release of Juju, juju-core 1.23.1, is now available.
This release may replace version 1.23.0 on Thursday April 23.
## Getting Juju
juju-core 1.23.1 is available for vivid and backported to earlier
series in the following PPA:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any insight on what I'm missing is appreciated. Another note is I'm
not quite sure if there is an alternative to getting the current
running environment other than doing a `juju switch local` then
running the plugin pulling in
Hello, i'm try to investigate gocharm and i'm happy with it.
But i'm stuck ad this issues:
https://github.com/juju/gocharm/issues/44
can somebody helps me?
--
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
jabber: v...@selfip.ru
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings
So if we want feature flagged providers I think the best option is to
change registration code path.
Probably my ideal would be to have
environs.RegisterFlaggedProvider(name, flag string, p EnvironProvider,
alias ...string)
and then we can track in environs/config.go that a given provider name is
