Skip to content

Latest commit

 

History

History
62 lines (48 loc) · 3.7 KB

PROJECTS.md

File metadata and controls

62 lines (48 loc) · 3.7 KB

Project Suggestions

These are intended to be more inspirational than prescriptive. If this list prompts a different idea, that's even better than snagging one of these. But if you'd like, feel free to run with anything on this list. Before claiming one, check the forks and see if you can join forces with someone already working on it.

  • Puppet 6 introduces Deferred functions, which are evaluated during catalog application time -- eg, agent-side functions. This provides functionality for all kinds of exciting things: secret management, data that must be looked up by the agent, registering with some service that responds with an authentication token, etc. What kind of exciting things could you think of? See an example project at puppet-vault-demo.

  • PQL is awesome and powerful, and like many things powerful it can be difficult to use. It would be great to have a graphical PQL editor and/or explainer. You can see some neat examples of something similar at https://regexr.com or at http://buildregex.com.

  • Bolt offers some intriguing new possibilities for deploying configuration changes. Write up a proposal for a workflow for applying ad-hoc but still repeatable configuration changes on-demand.

  • Speaking of Bolt, wouldn't it be great to have a Bolt-based acceptance test framework that's much easier to use than Beaker?

  • Types and Providers have long been a dark art. Recently though, we've released a new library to simplify the job. If there's always been that job you knew was suited for a type and provider, but didn't have the time to learn how -- now's the time. Build a new T&P or port an existing defined type to the Resource API.

  • The Puppet Server stack has been containerized, which opens us up to all sorts of nifty ideas. Perhaps you could put together a quick acceptance test automation framework using Pupperware. What else can you imagine?

  • Puppet Server now comes with a new CA command line tool and gem. It might be nice to have an open source graphical/web certificate management interface.

  • Do you have a favorite open source project? How are its docs? What about that one project? You know, the one with the default README.md created by GitHub... Maybe your project for this month could be writing documentation and a user guide.

  • Creating a Puppetfile is sometimes a tedious exercise. It would be much better if dependencies were resolved for you automatically. For that matter, there are many places in the Puppet ecosystem which would benefit from a dependency resolver. Perhaps you could build this in such a way that r10k could use it, the PDK could use it, etc. Maybe you could even wire up an external library to do the hard work for you.

  • Make it possible to store the CA on object storage to make the Puppet stack fully "cloud native" and stateless.

  • Port the augeasproviders_core library to the new Resource API to be used as an alternative base to build parsing providers.

  • Improve PDK to allow generating both documentation (README.md) and acceptance tests from examples in a unique directory. See https://github.com/raphink/puppet-freeradius (Rakefile, spec_helper_acceptance) for a PoC of that idea.

  • None of these look exciting? Check the forks and see if you can join an existing project.