[ 
https://issues.apache.org/jira/browse/WHIRR-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206690#comment-13206690
 ] 

David Alves commented on WHIRR-347:
-----------------------------------

bq. I would prefer that we stick to ENV variables (they are all scoped to 
WHIRR_ anyway + we can reduce boilerplate in bin/whirr for converting to system 
properties).

The thing is that without (mandatorily) using env variables we can have 
multiple installations each with its whirrrc file, besides testing for env 
variables within java is hacky.
As is it now you can still use env variables when needed, but these are 
transformed to script scope variables.

bq.Also I think we can have better defaults in whirrrc - aws ENV variables.

What so you suggest? whirr picking up aws env variables when none other are 
provided? (btw this is another reason not to require whirr_ env variables as if 
we implement this the user would expect the properties to change when he 
changes the aws ones, but they don't because previous script runs already set 
the whirr_ ones and the script would prefer whirr_ vs aws_)

If so I think this is a nice idea and will include it in the next patch.

Also the next patch does a much more thorough job of testing precedence (sys vs 
props vs args).

                
> 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, 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

        

Reply via email to