Closed ghost closed 3 years ago
Awesome! Thanks for the suggestions, I've accepted them now - ready for second review.
fwiw, bolt has bolt plan new proj_name::plan_name
with the optional -pp
flag. You get a YAML plan without the -pp
flag and you get a puppet language plan with the -pp
flag. I'd argue the plan examples should just be the same one from those commands.
The long term goal is to be able to run projects directly in PE and forgo the need to put them in a control-repo or module but this seems fine in the interim.
Hey folks,
Whenever any of my customers/prospects beginning using PE and the control repo, adding tasks and plans is always a bit of a mystery, especially when there's no template directories or files like there are for roles and profiles.
Given the maturity of tasks and plans at this point, we should really include something in the template control repo.
The
adhoc
directory withinsite-modules
contains atasks
andplans
directory.In the tasks directory I've included a skeleton for a nix and windows based task with some basic task metadata (environment + task description). I've also included a plan with a description and targets param.