-
-
Notifications
You must be signed in to change notification settings - Fork 0
PDK Conversion Guide #1
Comments
I think this repository shouldn't be named the same as https://github.com/puppetlabs/pdksync because that's confusing. Should it be Edit: have you considered directories within a single repository? |
This is a great suggestion. I think directories will be required at some point to support some customization for grouping of some sort. For now we just have the single use case. Was there something you had in mind? |
FYI: I pinged Puppet Inc (again) about gems build for Ruby 2.7: puppetlabs/puppet-module-gems#127 |
The voxpupuli-test gem is causing issues with pdk.
|
I don't know why we pin to 1.15.0 specifically in voxpupuli-test but a PR there is welcome. On a side note: I think we should avoid the My ideal scenario is that modulesync_config can be used as a PDK template repository. This would allow us to have the benefits on the PDK (are there any?) without the downsides of pdk-templates. |
I recently added a doc around managing templates: https://github.com/voxpupuli/pdk-templates/blob/vp-latest/VP_README.md Also the puppet-format module runs on pdk already as the guinea pig. The acceptance test stuff is missing ATM as I would need to learn how this is currently accomplished with modulesync and travis. Here is an example travis run: What we have is a good start but definately need some refinements from those who know the vox workflow as I don't. |
PDK Templates conversion guide
This document serves as the steps required to convert voxpupuli organization to start using the pdk on current and future puppet nodules.
Please note this is an opt-in strategy as to not cause disruption with existing modules.
Step 1 (Pdk-templates):
Future pdk-template updates will follow this workflow:
This gives us the ability to add in our own changes, as we will likely have different opinions on which files are included in the templates by default.
Step 2: (PDKSync )
Step 3: Convert or Create modules with PDK at will
Since this can be done in a number of ways I have outlined all the possibilities and provided a workflow for each method
Existing Puppet Module Conversion Workflow using pdksync
PDK Puppet Module Conversion Workflow using pdk
New Puppet Module Workflow using pdk
Notes
https://github.com/puppetlabs/pdk-templates
https://github.com/puppetlabs/pdksync
The text was updated successfully, but these errors were encountered: