This is an interesting one, I hacked together a one-liner from both Nate
and your replies
juju ssh 0 "ps -ae -o command= | grep [j]ujud | grep JUJU_DEV_FEATURE_FLAGS
| awk -f'\"' '{ print $2 }'"
and added[0] it to the juju plugins repo as `juju flags`:
https://github.com/juju/plugins
$ juju flags
storage jes
Marco
[0]: https://github.com/juju/plugins/pull/61
On Tue, Sep 22, 2015 at 3:59 PM Andreas Hasenack <andr...@canonical.com>
wrote:
> On Tue, Sep 22, 2015 at 4:57 PM, Tim Penhey <tim.pen...@canonical.com>
> wrote:
>
>> On 23/09/15 05:18, Andreas Hasenack wrote:
>> > Hi,
>> >
>> > given an existing juju environment, is there a way to tell which
>> > JUJU_DEV_FEATURE_FLAGs were used to bootstrap it?
>> >
>> > I'm using 1.24.6
>>
>> The second line of logging in every agent lists the feature flags that
>> the agent is using.
>>
>> As the agent starts it logs first the version of juju, then the feature
>> flags.
>>
>>
>
> Got it there too, thanks:
> machine-0: 2015-09-22 19:36:19 INFO juju.cmd.jujud machine.go:419 machine
> agent machine-0 start (1.24.5-trusty-amd64 [gc])
> machine-0: 2015-09-22 19:36:19 WARNING juju.cmd.jujud machine.go:421
> developer feature flags enabled: "address-allocation"
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
