Storage vs. PublicStorage
Jeroen Vermeulen
jtv at canonical.com
Tue Mar 12 04:36:22 UTC 2013
Hi all,
We just noticed that the documentation for Environ.PublicStorage() has
been updated. It no longer says that the public storage is optional,
and now it explains that this storage is meant to be shared between
environments.
This combination is problematic for our ongoing provider implementation.
So my question is: would it actually be a problem if our
PublicStorage() were not shared between environments? For instance, a
very simple thing for us to do would be to have Storage() and
PublicStorage() return the same Storage.
Jeroen
More information about the Juju-dev
mailing list