[
https://issues.apache.org/jira/browse/BIGTOP-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039083#comment-14039083
]
Konstantin Boudnik commented on BIGTOP-1047:
--------------------------------------------
I think the important part is to make sure that individual schedules do not
block other people's effort. Hence, if 3.x support isn't affected by the
possible changes in the current master - anything radical yet to be seen,
honestly - then 3.x effort should proceed on a branch.
> Support Puppet 3.x
> ------------------
>
> Key: BIGTOP-1047
> URL: https://issues.apache.org/jira/browse/BIGTOP-1047
> Project: Bigtop
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 0.6.0
> Reporter: Andrey Klochkov
> Attachments: BIGTOP-1047--n2.patch, BIGTOP-1047.patch
>
>
> Currently bigtop-deploy/puppet module supports Puppet 2.x only. In
> particular, this is because of using dynamic scoping which was deprecated
> since 2.5 and not supported in 3.x. This task is to get rid of dynamic
> scoping to make bigtop-deploy/puppet working with Puppet 3.x.
> More on dynamic scoping in Puppet:
> http://docs.puppetlabs.com/guides/scope_and_puppet.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
