whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Heneveld (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-415) Let users specify the CDH release (cdh3u1, cdh3u2)
Date Wed, 09 Nov 2011 12:36:51 GMT

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

Alex Heneveld commented on WHIRR-415:
-------------------------------------

Personally I don't like overloading {{tarball.url}} in this way.

What if we had a more general mechanism for allowing environment variables to be specified
in the config file?

I am thinking something like:

{code}
env.someVar=value
{code}

Then {{SOME_VAR=value}} is exported and available to the scripts, so we could say {{env.repo=cdh3u1}}
to solve this problem.

Interested to know people's thoughts, if this is a good idea, if {{env.SOME_VAR}} syntax is
more intuitive (and if this should be a separate jira).
                
> Let users specify the CDH release (cdh3u1, cdh3u2)
> --------------------------------------------------
>
>                 Key: WHIRR-415
>                 URL: https://issues.apache.org/jira/browse/WHIRR-415
>             Project: Whirr
>          Issue Type: Improvement
>          Components: service/cdh
>            Reporter: Andrei Savu
>            Priority: Critical
>             Fix For: 0.7.0
>
>         Attachments: WHIRR-415.patch
>
>
> Allow explicit selection of the CDH release you want to use. The current behaviour is
to use the latest one. 

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

        

Mime
View raw message