It is likely that an admin will want to validate that the charm code will be successful after a series upgrade before issuing the juju upgrade-series <machine> complete command. However, the current logic will only trigger on the post-series-upgrade hook which doesn't allow the admin a chance to validate the new venv.
I think we should add a --rebuild option to the charm-env command which does the venv rebuild manually and presumably sets a flag to indicate to the bootstrap code that it has already been rebuilt for the current series so that it doesn't get rebuilt again upon post-series-upgrade.
It is likely that an admin will want to validate that the charm code will be successful after a series upgrade before issuing the
juju upgrade-series <machine> completecommand. However, the current logic will only trigger on thepost-series-upgradehook which doesn't allow the admin a chance to validate the new venv.I think we should add a
--rebuildoption to thecharm-envcommand which does the venv rebuild manually and presumably sets a flag to indicate to the bootstrap code that it has already been rebuilt for the current series so that it doesn't get rebuilt again uponpost-series-upgrade.