Products · Product
Puppet
Raised as a usability problem by 21 people on Hacker News over 15 years (2009–2023), in 18 threads.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
Every issue, all time, most people first
Testing Puppet configurations locally is harder than with ChefUnreviewed
20092026- Hard to test Puppet configurations locally compared to Chef2020-04-16
- Extra indirection: must map Puppet module settings onto the tool's actual configuration2019-05-23
- No good way to test Puppet changes before deploying them2011-03-08
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 22 complaints
- Developers must learn Puppet and troubleshoot failed runs, plus RPM packaging pitfalls2023-07-28
- Commenter leaves the site repeatedly because they can't tell where to start2022-07-03
- Homepages bury the basic tool under enterprise products; tutorials demand heavy setup2020-11-17
- Hard to test Puppet configurations locally compared to Chef2020-04-16
- Extra indirection: must map Puppet module settings onto the tool's actual configuration2019-05-23
- Reference documentation is hard to find, buried and scattered across the site2017-05-18
- Fails in ways that can't be diagnosed even with debug on2016-03-10
- Puppet documentation is horrible for newbies and errors are uninformative2015-10-16
- Puppet's DSL has many gotchas that trip up developers unfamiliar with it2014-08-05
- Parser breaks with every release and is hard to test locally2014-08-05
- Configuration DSLs are hard to reason about; debugging deep backtraces to find simple failures2014-03-15
- Easy to forget ordering, causing intermittent hard-to-debug failures2013-11-09
- Building reusable components is nearly impossible without hacky workarounds2013-06-24
- Many modules have no or vague docs, making setup hard to trace2013-03-04
- Table of contents only covers current section, so user loses their place in docs2011-10-09
- Download link leads through registration page; must scroll to bottom to skip2011-05-03
- Open source edition download is hidden behind multiple forms and pages2011-05-03
- The ensure parameter overloaded with four different meanings, confusing to use2011-03-08
- No good way to test Puppet changes before deploying them2011-03-08
- Documentation lacks valid examples and a unified syntax reference, hard to navigate2011-03-08
- Error messages are next to useless, often not pointing to the file or line with the error2010-12-20
- Puppet is a pain to set up2009-04-06