[
https://issues.apache.org/jira/browse/BIGTOP-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342734#comment-14342734
]
Evans Ye commented on BIGTOP-1627:
----------------------------------
Indeed that would be a great feature to have, and would be a much elegant,
bolder solution than this one. We probably need to loop over the array if
puppet's native resource does not support. From my point of view, can we have
this *at least work* version in and then head to the uri array attempting?
> Move enable_local_yum implementation to bigtop-deploy/utils/setup-env.sh to
> share with Docker provisioner
> ---------------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-1627
> URL: https://issues.apache.org/jira/browse/BIGTOP-1627
> Project: Bigtop
> Issue Type: Improvement
> Affects Versions: 0.8.0
> Reporter: Evans Ye
> Assignee: Evans Ye
> Priority: Minor
> Labels: deployment, vm
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1627.1.patch, BIGTOP-1627.2.patch,
> BIGTOP-1627.3.patch, BIGTOP-1627.4.patch, BIGTOP-1627.5.patch
>
>
> Currently, we have *enable_local_yum* feature implemented in
> *vagrant-puppet-vm*'s Vagrantfile(see BIGTOP-1562's patch). This jira is
> proposing to move the implementation to {{bigtop-deploy/utils/setup-env.sh}}
> so that the we can share the general implementation between BigTop's VM
> provisoner and Docker provisioner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
