When chaining tests that contain a relationship configuration change its currently required to destroy the environment. It would be a tighter experience and cut down on redeployment time in automated testing environments to upgrade charms on each test run.
Can we make sure amulet runs an upgrade each time the deployer runs?
--snip--
<lazypower> nope, i chained right off of the standup test
<lazypower> let me clear and try fresh
<marcoceppi> lazypower: that's the problem
<marcoceppi> lazypower: the relation-sentry doesnt' get upgraded, so it doesn't get the latest metadata.yaml
<lazypower> i just hit the setup() portion of the test, so far so good
<lazypower> ahhh ok
<marcoceppi> so technically relation-sentry doesnt have those defined yet
<lazypower> so the sentries cache data then
<marcoceppi> lazypower: no, the deployment caches data
<lazypower> whatever config comes in initially they hold on to, and are not reprogrammable
<marcoceppi> its a juju feature, can you open a bug to make sure that amulet runs an upgrade each time deployer runs?
<lazypower> sure, against amulet right?
<marcoceppi> lazypower: yes
<marcoceppi> lazypower: I think I just need to add the --update-charms flag to deployer
--
This appears to no longer be an issue as it was resolved in deployer upstream
-- snippet from kapils email --
As of 1.17 (on both client and environment) For local charms, juju will always upload a new version on deploy and upgrade, so need to worry about cached charms in the state server being used even when you have a new changes in the charm.