[
https://issues.apache.org/jira/browse/BIGTOP-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341341#comment-14341341
]
Konstantin Boudnik commented on BIGTOP-1693:
--------------------------------------------
Perhaps then it would make sense to enforce Puppet 3x installation at the
higher level somewhere? Eg perform a check and throw an Error instead of
documenting the requirement? In my experience docs are rotting out pretty
easily unless someone has a job to support them ;)
How do you feel about taking care of this enforcement in a separate JIRAs to
avoid mixing different topics in one commit?
> Puppet stdlib should be automatically installed by toolchain
> ------------------------------------------------------------
>
> Key: BIGTOP-1693
> URL: https://issues.apache.org/jira/browse/BIGTOP-1693
> Project: Bigtop
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 0.8.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Fix For: 0.9.0
>
> Attachments:
> 0001-BIGTOP-1693.-Puppet-stdlib-should-be-automatically-i.patch,
> BIGTOP-1693.patch, BIGTOP-1693.patch, BIGTOP-1693.patch, BIGTOP-1693.patch,
> BIGTOP-1693.patch
>
>
> Right now we have an explicit instruction for a user to install puppet stdlib
> before doing the deployment. This is a bad UX.
> I think the installation should be done in the
> {{bigtop_toolchain::deployment_tools}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
