=== ChanServ changed the topic of #juju-dev to: https://juju.ubuntu.com | On-call reviewer: - | Bugs: 8 Critical, 68 High - https://bugs.launchpad.net/juju-core/
=== meetingology` is now known as meetingology
[08:03] <rogpeppe> mornin' all
[09:53]  * fwereade_ lunch
[11:31] <danilos> mgz, dimitern, hi, I'm not feeling well enough to have a call now, will likely file a sick day :/
[11:32] <dimitern> danilos: ok, get well soon!
[11:32] <danilos> dimitern, cheers
[11:33] <mgz> okay dimitern.
[11:33] <mgz> call anyway, or just crack on?
[11:34] <dimitern> mgz: can we just skip it today?
[11:34] <mgz> sure.
[11:34] <dimitern> cool
[11:40] <mgz> btw poke me for ocr reviews everyone. I'll leave some comments in Ian's branches
=== marcoceppi_ is now known as marcoceppi
=== wedgwood_away is now known as wedgwood
[15:36] <marcoceppi> I was poking around the help for juju-core 1.10, what version (if any) can you specify an alternate .juju/environments.yaml (or different .juju "home")?
[15:36] <marcoceppi> I didn't see it in the help docs in 1.10
[15:43] <fwereade_> marcoceppi, 1.10 will respect the JUJU_HOME env var, in which yu can put your alternative environments.yaml
[15:43] <marcoceppi> fwereade_: thanks, that's what I was looking for!
[15:44] <fwereade_> marcoceppi, yw :)
[15:54] <rogpeppe> marcoceppi: there's also JUJU_ENV
[15:54] <rogpeppe> marcoceppi: i think py and go environments can coexist in the same file if you want
[15:54] <sidnei> oh, that's something i hadn't thought about
[15:54] <marcoceppi> rogpeppe: I have a few that do, but this was specifically for juju-testing which has an --isolate option I'm trying to replicate
[15:55] <marcoceppi> Which leads me to my next question
[15:56] <marcoceppi> In pyjuju there's a DELEGATE_CHARM and DELEGATE_REPOSITORY environment variable that _can_ be set (according to the jitsu test code). Does this notion exist in the go version?
[16:00] <fwereade_> marcoceppi, sorry, I don't think so -- what's it for? is it perhaps jitsu-specific?
[16:01] <marcoceppi> fwereade_: I think it was something baked in to pyjuju for testing specifically. I'm not too worried about it for go-juju at this point, but I think it was a way to get around having juju deploy <charm> actually do a local deploy /instead/ of from cs
[17:41] <rogpeppe> right, i'm done
[17:41] <rogpeppe> g'night all
=== wedgwood is now known as wedgwood_away
=== Makyo is now known as Makyo|out