Late to this thread, but I had to add a few things to this resource
discussion.
In my experience with charm development zero byte resources has been
beneficial in three areas, charm development, third party charms, and
testing.
*Charm development*. When creating a new charm that uses resources,
Correct, the original discussion was the charm behaving differently if the
fingerprint had changed of the resource on the remote end. However, running
resource-get deals with only fetching the new data if the fingerprint
changes and so there wasn't a big draw to the feature to that end.
Now, in
We initially asked for resource fingerprints to be available before
fetching so we could do something less expensive.
That didn't make the 2.0 cut and was pushed back needing more forethought.
This however is a good example of why it's a better option.
And I had similar logic in etcd at one
