-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new control
command for creating control repository
#333
Comments
@bittner except for the metadata.json check the validation will work on existing control repo so far that I can tell. |
The The Not sure how the |
I was talking with my team about adopting PDK, and the files PDK adds when it converts modules, so that it can run the tests and validation. Currently our control repo has 40+ internal Puppet modules, and converting them all with PDK would potentially add a huge number of duplicate files (Gemfile etc). It would be good to know if support for testing across control repos is still on the development plan. I am hopeful we will eventually be able migrate our TravisCI setup to test our control repo solely using simple PDK commands |
Additional question, has any thought been given to integrating the onceover gem into PDK for control repo testing? |
I'd second onceover. PDK is to modules as onceover is to control repos (as it stands today). |
This issue was moved to puppetlabs/pdk-planning#10 |
PDK should support creating and extending a control-repository, which is enabled for validation and testing using PDK (just like the modules created by PDK).
Obsoletes #289 and #332 when implemented.
See also: puppetlabs/control-repo#52
Proposed Solution
Ideally,
pdk new control
command should generate a control-repo setup that is equivalent to the proposed Puppet Labs control-repo on GitHub.This way, whether you use PDK or just the GitHub repo as an example, you can trust to get a usable best-practice setup.
The text was updated successfully, but these errors were encountered: