You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "David Alves (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/02/09 07:27:59 UTC
[jira] [Issue Comment Edited] (WHIRR-347) Support
provider-independent environment variables for cloud credentials
[ https://issues.apache.org/jira/browse/WHIRR-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204304#comment-13204304 ]
David Alves edited comment on WHIRR-347 at 2/9/12 6:27 AM:
-----------------------------------------------------------
Here's what I did:
there are now the following env variables:
WHIRR_PROVIDER
WHIRR_IDENTITY
WHIRR_CREDENTIAL
WHIRR_BLOBSTORE_PROVIDER
WHIRR_BLOBSTORE_IDENTITY
WHIRR_BLOBSTORE_CREDENTIAL
whirr now expects properties to come from (in order of preference, ie later values will take precedence (override) previous ones):
1 - values in whirr/conf/whirrrc
2 - values in ~/.whirr/whirrrc
3 - environment variables
4 - arguments passed in the command line
4 - properties file
- In a typical use case the user would maintain a whirrrc file in ~/.whirr with the credential details.
- For punctual cases where the user wants to switch providers temporarily he/she can set the environment variables (they override whirrrc)
- For a single command in another provider args can be used as always (which override the previous methods)
- Also as always recipes can also have the config (which overrides everything)
if specifically set blobstore creds will follow the same procedure. if after everything is loaded blobstore creds are still missing then they are set to null (so that whirr can load the compute ones in its place, as usual)
maven builds and unit tests pass
was (Author: dr-alves):
Here's what I did:
there are now the following env variables:
WHIRR_PROVIDER
WHIRR_IDENTITY
WHIRR_CREDENTIAL
WHIRR_BLOBSTORE_PROVIDER
WHIRR_BLOBSTORE_IDENTITY
WHIRR_BLOBSTORE_CREDENTIAL
whirr now expects properties to come from (in order of preference, ie later values will take precedence (override) previous ones):
1 - values in whirr/conf/whirrrc
2 - values in ~/.whirr/whirrrc
3 - environment variables
4 - arguments passed in the command line
4 - properties file
- In a typical use case the user would maintain a whirrrc file in ~/.whirr with the credential details.
- For punctual cases where the user wants to switch providers temporarily he/she can set the environment variables (there override whirrrc)
- For a single command in another provider args can be used as always (which override the previous ones)
- Also as always recipes can also have the config (which overrides everything)
is specifically set blobstore creds will follow the same procedure, if after everything is loaded blobstore creds are still missing then they are set to null (so that whirr can load the compute ones as usual)
maven builds and unit tests pass
> Support provider-independent environment variables for cloud credentials
> ------------------------------------------------------------------------
>
> Key: WHIRR-347
> URL: https://issues.apache.org/jira/browse/WHIRR-347
> Project: Whirr
> Issue Type: Improvement
> Reporter: Tom White
> Assignee: David Alves
> Fix For: 0.8.0
>
> Attachments: WHIRR-347.patch
>
>
> Adrian suggested that we support WHIRR_PROVIDER, WHIRR_IDENTITY, WHIRR_CREDENTIAL environment variables. This would allow users to set them for any cloud they are using.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira