Some initial thoughts and stuff I would do.

1. run pdk convert inside control repo
2. name the module control_repo inside metadata
3. Alter supported operating systems for the entire code base
4. Add dependencies and generate fixtures file from Puppetfile
5. Ensure site-modules dir gets in included in tests/validation
6. Allow testing of site.pp file via node level tests created automatically like pdk new class

Just to provide some context from the pdk validate side of things for control repos, there's very little validation being performed other than the environment.conf being checked for these ALLOWED_SETTINGS.

Thought I'd convey what was garnered from https://github.com/puppetlabs/devx/issues/15

This issue has been marked stale because it is open with no recent activity. The PDK Team is actively prioritizing existing bugs and new features, if this issue is still important to you please comment and we will add this to our backlog to complete.

Is this still going to happen? I really want to try using pdk to validate my control-repos, but I'm still trying to figure out exactly how it works, what it does, and how exactly to do it. I only found this issue after half an hour of searching across google, github, and the community slack.

Hi @wilrodriguez

We are currently working on the next generation of the PDK (see this blog post for more details). Control repo support is something on our roadmap for the new PRM (Puppet Runtime Manager) tool.

We'll communicate out to the Community Slack when we have an early access build available. The roadmap and early access releases will be available in the PRM repo itself. Expect to see tickets for control-repo support soon - we're still in the planning phases of this functionality.

Sorry you had quite a bad experience trying to find this issue. We're working on a dedicated website to act as a portal / single entry point for the tooling the DevX team is responsible for. Hopefully this will mean it's easier to get information
/ submit feedback about the tooling.

This issue has been marked stale because it is open with no recent activity. The PDK Team is actively prioritizing existing bugs and new features, if this issue is still important to you please comment and we will add this to our backlog to complete.