Introducing, juju resources!

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2016-02-13 09:10 AM, Rick Harding wrote:
> Your read is correct. You must declare the resources. It's helpful
> to users to know what to stick in there and for the charm to be
> able to handle different items. In your case, a single tar file of
> the plugins you'd like to enable could be sent up and the charm
> would be able to untar, loop through them, etc. Ideally the charm
> would be uploaded to the store with a standard set of plugins and
> folks could then customize which ones they wanted by creating their
> own tar of plugins.

Another use case is when you want to create a charm deploys Python
code.  You want it to use "resources" instead of downloading
dependencies from PyPI.

1. The list of resources can change over time.  You don't want the
charm to have to change every time the deployed software adds/removes
a dependency.

2. The version numbers are embedded in the filenames.  You don't want
the charm to have to change ever time deployed software changes its
version numbers.

Yes, you can work around this with tarfiles, but why do we want to?
It's a pain to build a tar file every time a single dependency
changes.  It's easier to use S3 instead for a particular use case, but
it doesn't solve the general case.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWwL5XAAoJEK84cMOcf+9hVLQIAI5q7epn8UKtAILu9E41PoPK
CzVE+8gkWHEOZ9fOpfC8rXGVl1MmF279vx7o5eEYaXq8LNIL4yQx4rg4BahnkIhn
oO5LwPLXTp6c+XJ6muofqQZtvm80HJO3AcsuYbdrQoBDrQrNqjPr4yMXZi0BJ1c1
iGmqNTgl4IWfYJtxMGmzV7qBLrjepG17lClHSNFpMz4rpftZje7H0utPsoFvFRcU
ya0LiGiKjTgkBfPWuopgO6cBZ8Y0FVPV94tyLc67PNrjSYDYKeSrfMCAMdHZ4Gh9
kMM4pnEjX0lT01d8A8PcecbmUDRJ1NLHnzDW1VeJxDXVrzA/vIMF+QWc0EUJKCo=
=BEaN
-----END PGP SIGNATURE-----