Re: Which JUJU_DEV_FEATURE_FLAG were used?

On Tue, Sep 22, 2015 at 3:00 PM, Nate Finch wrote: > The environment variables are transferred to the server, so getting them > from /proc//environ on the server should be doable (someone better at > bash might be able to give you a one liner). > > Thanks. For

Re: Which JUJU_DEV_FEATURE_FLAG were used?

On Tue, Sep 22, 2015 at 4:57 PM, Tim Penhey 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

Re: Which JUJU_DEV_FEATURE_FLAG were used?

The environment variables are transferred to the server, so getting them from /proc//environ on the server should be doable (someone better at bash might be able to give you a one liner). On Tue, Sep 22, 2015 at 1:19 PM Andreas Hasenack wrote: > Hi, > > given an existing

Which JUJU_DEV_FEATURE_FLAG were used?

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 -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju

Re: Which JUJU_DEV_FEATURE_FLAG were used?

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