Going back to the bug Aaron submitted, if we have a substrate that Juju is pulling invalid instance-types for then that needs to be fixed in Juju, not our tests. If that means our tests break until they fix it then that's what happens. I agree with his statement that Juju should work 'out of the box' in all 2.0 cases.
Regarding being used in models, is that in our own code? I'm not sure what you mean there.
I'm going to revert the restore_backup change, but I would like to hear your thoughts before I merge this.
Going back to the bug Aaron submitted, if we have a substrate that Juju is pulling invalid instance-types for then that needs to be fixed in Juju, not our tests. If that means our tests break until they fix it then that's what happens. I agree with his statement that Juju should work 'out of the box' in all 2.0 cases.
Regarding being used in models, is that in our own code? I'm not sure what you mean there.
I'm going to revert the restore_backup change, but I would like to hear your thoughts before I merge this.