Skip to content

Integrate with Vox Pupuli #570

Open
Open
@bastelfreak

Description

Use Case

We talked a lot about it between Vox Pupuli members and some Puppet employees. We (Vox Pupuli) have some gems to structure our tooling, for example:

  • voxpupuli-test
  • voxpupuli-acceptance
  • voxpupuli-release

Those map to unit tests and static code validation, acceptance testing, releasing a module.

Describe the Solution You Would Like

I think we should work out a plan to more align the Vox Pupuli and Puppet tooling and what's templated. We try to provide as little boilerplate as possible in our modulesync_config (our pdk-templates equivalent). That makes updates way easier. I think that's something we should work towards to for Puppet as well. I think we should have a talk in zoom or slack about the differences and what we can unite.

Describe Alternatives You've Considered

A clear and concise description of any alternative solutions or features you've considered.

Additional Context

For the whole ecosystem it makes ense when the two biggest module maintainers, Vox Pupuli and Puppet, work together. That also makes it easier for pdk for calling the different tasks.

CC: @davidsandilands I think you mentioned similar ideas at the beginning of the year.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions