There are plans in Juju to treat snap resources for machine operators as it does OCI resources for kubernetes operators - that is, there is a 1:1 mapping between the charm revision and the resource revision. This feels like the most appropriate way to do this from the charm.
The current problem is that there is just a broad disconnect between the snap and charm stores/revisions. It is far better to have the charm/snap pairing and deliver it that way. That's a future juju improvement.
The workaround should work, as Alex referred to in comment #7, but now has the problem that the payload and the charm differ. That's actually probably okay for the time being.
There are plans in Juju to treat snap resources for machine operators as it does OCI resources for kubernetes operators - that is, there is a 1:1 mapping between the charm revision and the resource revision. This feels like the most appropriate way to do this from the charm.
The current problem is that there is just a broad disconnect between the snap and charm stores/revisions. It is far better to have the charm/snap pairing and deliver it that way. That's a future juju improvement.
The workaround should work, as Alex referred to in comment #7, but now has the problem that the payload and the charm differ. That's actually probably okay for the time being.