=== frankban|afk is now known as frankban
[13:01] <frankban> wallyworld: do you have time to look at https://github.com/juju/juju/pull/7563 ?
[13:12] <wallyworld> frankban: it doesn't look right - there is no application level workload version. workload version is set b the charm, and ech unit potentially can run a separate charm revision until any upgrades sync across all units
[13:15] <frankban> wallyworld: it's kind of an abstraction, the version set by the last unit wins, similar to the application status
[13:15] <wallyworld> with status, that  is meant to only be set by the leader, so it's not really last one wins there
[13:16] <frankban> wallyworld: 99% of the times the version is the same for all units, and "juju status" already uses that abstraction (version is displayed in the applications section, for each application)
[13:16] <wallyworld> agree it is the same 99% of the time but the other 1% we are lying
[13:17] <frankban> wallyworld: and we are already lying in "juju status"
[13:17] <wallyworld> if others think it's ok to do this then it's ok i guess
[13:17] <frankban> wallyworld: I mean, I am just trying to meet users expectations, and they want in the gui something similar to what they get in juju status
[13:18] <frankban> wallyworld: we can add the more exact version in the unit info later if required
[13:18] <wallyworld> that is fair enough, if it just matches status then it's no better or worse
[13:18] <wallyworld> sgtm
[13:18] <wallyworld> i didn't realise we were matching status
[13:21] <frankban> wallyworld: ty
[13:21] <wallyworld> frankban: np, sorry for pushing back a bit, i just wanted to be sure we were doing the righy thing
[13:22] <frankban> wallyworld: np
=== cholcombe_ is now known as cholcombe
=== frankban is now known as frankban|afk