deploy map-machines=existing does not handle updated resources

[Dmitrii Shcherbakov]

After changing bundle resources and redeploying with map-machines=existing `juju resources` shows the same revision for all resources as before and no events are generated for charms.

Steps to reproduce:

1) deploy any charm with resources defined

bundle.yaml:
...
    resources:
      idp-metadata: "/tmp/tmpfile.xml"
      sp-signing-keyinfo: "/tmp/otherfile.xml"
      sp-private-key: "/tmp/testfile.pem"

... Executing changes:
- upload charm /home/dima/src/canonical/openstack/charm-keystone-saml-mellon/build/builds/keystone-saml-mellon for series xenial
- deploy application keystone-saml-mellon on xenial using /home/dima/src/canonical/openstack/charm-keystone-saml-mellon/build/builds/keystone-saml-mellon
  added resource idp-metadata
  added resource sp-private-key
  added resource sp-signing-keyinfo ...

2) change resources to point to new files

bundle.yaml:
...
    resources:
      idp-metadata: "/tmp/newtmpfile.xml"
      sp-signing-keyinfo: "/tmp/newotherfile.xml"
      sp-private-key: "/tmp/newtestfile.pem"

3) deploy the same bundle with map-machines=existing

... # no relevant "added resource output"
Executing changes:
- set application options for neutron-api
...

juju status -m controller
Model Controller Cloud/Region Version Notes SLA
controller vmaas vmaas 2.3.6 upgrade available: 2.3.7 unsupported

App Version Status Scale Charm Store Rev OS Notes

Unit Workload Agent Machine Public address Ports Message

Machine State DNS Inst id Series AZ Message
0 started 10.10.101.80 cmfcxx xenial default Deployed

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.