`juju diff-bundle` export includes charm pinning

[Dan Ackerson]

`juju diff-bundle` is extremely helpful for Field when making a clone of a customer cloud.

However, this export contains all of the current versioning (pinning) of the installed charms which must then be manually removed in order to create a valid CPE deployment bundle.

Perhaps an option to export w/ version info would be more appropriate?

[Richard Harding (rharding)]

 Thanks for filing the request. Why do the revisions need to go away to validate? It seems odd to me as "the model" is specific to the charms at play, the config, etc. Taking part of that out seems like it is a less effective method of having something work in the future.

[Vern Hart (vern)]

When comparing the bundle/overlays for a new deployment to an older deployment, we don't care as much about charm revisions/channels as we do about bindings, options, etc. Having the option to turn off charm, channel, etc., would reduce the noise for seeing what configs we may have forgotten to include in the new deployment.