This is because puppet tasks were implemented first and plans came later. If it would help reduce confusion, we could create a Puppet[:plans] setting that is an alias for Puppet[:tasks]. In other words, you could pass either --tasks or --plans, but we'd prefer and document --plans (similar to what we do for serverport & masterport).
from `puppet parser validate` I would expect to validate all code, manifests and plans... `puppet parser validate` should validate manifests and plans
This part is filed as PUP-9578, so please follow that ticket for updates.
the validate/syntax rake task from puppetlabs_spec_helper should validate plans as well.
Please file a PDK ticket for that. It seems like puppetlabs_spec_helper could detect if the plans directory exists and if so, enable tasks/plans and validate just manifests in that directory. /cc Ben Ford |