This change has some implications if I am not wrong when it comes to persist the credentials across different contexts.
Currently, the [CredentialStoreModule constructor](https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/rest/config/CredentialStoreModule.java#L55-L57) accepts a `Map<String, InputStream>` that was supposed to be a blob store backed map. If you take a look at the [documentation in the main site](http://jclouds.incubator.apache.org/documentation/userguide/compute/) (scroll down to the "working with credentials" section) you'll see that the map was built using the removed methods from the `BlobStoreContext`. I am in favor of removing these maps too, but perhaps we should provide a way to keep using a persistent credential store in an easy way? There was [a discussion time ago](https://groups.google.com/forum/#!topic/jclouds-dev/PnDxfIDfwow) about the semantics of the `InputStreamMap`, and one suggested approach was to replace it by a `LoadingCache`. Could it make sense to implement a similar behavior using it? Again, I like removing this, just want to make sure we don't leave users using a persistent credential store without an alternative (worth a JIRA)? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/153#issuecomment-25075965
