[PDK-378] Enable the Modules team to use the PDK Created: 2017/08/03  Updated: 2018/08/31  Resolved: 2018/08/31

Status: Closed
Project: Puppet Development Kit
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Epic Priority: Normal
Reporter: David Schmitt Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: road-to-supported
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: Enable the Modules team to use the PDK
QA Risk Assessment: Needs Assessment


Opportunity: While the PDK v1 already provides good guidance to New Developers, folks with existing modules are left out cold, having to manually move their content over to the new structures. A process to help them migrate onto the PDK will enable them to unlock the value in the PDK tooling.

Definition: To have a in-house customer, we can leverage the Module Team's experiences and workflows as an approximation of what our biggest developer groups have to go through. The two main problems to be solved are

  • bringing existing modules into the PDK fold ("convert")
  • update a module from one template version to the next ("updating")
  • build and publish the module to the forge ("publish")

Comment by Jesse Scott [ 2018/08/31 ]

I know this isn't 100% "done" (pdk publish doesn't exist yet) but that is going to be it's own Epic and we generally don't nest epics inside other epics. Seems silly to leave this open and blocked by a not yet created epic.

Generated at Sat Aug 08 16:54:59 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.