Comment 0 for bug 2034206

Hi,

It is a copy of request from MM:
https://chat.charmhub.io/charmhub/pl/46woqta5b7ghipnu8d39khdbwo

At the moment, the air-gapped deployments happens in way:

> juju download mysql --channel 8.0/edge
Fetching charm "mysql" revision 188 using "8.0/edge" channel and base "amd64/ubuntu/22.04"
Install the "mysql" charm with:
    juju deploy ./mysql_r188.charm

> ls *.charm
mysql_r183.charm mysql_r188.charm postgresql-k8s_r73.charm

> juju deploy ./mysql_r188.charm
Located local charm "mysql", revision 0
Deploying "mysql" from local charm "mysql", revision 0 on ubuntu@22.04/stable

As you can see the revision got dropped from "188" to "0".
It creates a lot of confusion and unnecessary complexity on upgrades.

Goal: invent possibility to deploy juju charms into air-gapped installations holing the charmhub revisions.

P.S. It is already avaiable for SNAPs as store has a concept of ".asserts:
which are downloaded together with .snap file:

> snap download charmed-mysql --edge
Fetching snap "charmed-mysql"
Fetching assertions for "charmed-mysql"
ls Install the snap with:
   snap ack charmed-mysql_69.assert
   snap install charmed-mysql_69.snap

> ls -la
-rw-rw-r-- 1 ubuntu ubuntu 5635 Sep 5 13:24 charmed-mysql_69.assert
-rw------- 1 ubuntu ubuntu 111820800 Sep 5 13:24 charmed-mysql_69.snap

> grep revision charmed-mysql_69.assert
snap-revision: 69

Unfortunately .assert concept is missing for charmhub.io currently.
I hope, it can be included in the nearest roadmap.
Thank you!