[
https://issues.apache.org/jira/browse/WHIRR-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer updated WHIRR-706:
-------------------------------
Attachment: WHIRR-706.patch
I thought about this, and decided that it's actually fairly reasonable not to
include the credential, but then we need a way to invalidate the cached context
for an identity/endpoint/provider combination. Hence, adding an
invalidate(ClusterSpec) method.
> ComputeCache doesn't make new compute service for same identity/different
> credential
> ------------------------------------------------------------------------------------
>
> Key: WHIRR-706
> URL: https://issues.apache.org/jira/browse/WHIRR-706
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.1
> Reporter: Andrew Bayer
> Assignee: Andrew Bayer
> Attachments: WHIRR-706.patch
>
>
> If you provide an incorrect credential, and then in the same JVM, try again
> with a correct credential, ComputeCache still gives you the old one - it
> compares based on provider/endpoint/identity but not credential. This is
> fairly annoying if you're trying to, say, use Whirr as the guts of a web-app.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
