[PUP-9153] Puppet Task metadata should support task spec revision 3 Created: 2018/09/18  Updated: 2018/10/02  Resolved: 2018/09/24

Status: Closed
Project: Puppet
Component/s: None
Affects Version/s: None
Fix Version/s: PUP 6.0.1

Type: Improvement Priority: Normal
Reporter: Michael Smith Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks BOLT-752 Puppet should not error on unknown ke... Resolved
Template:
Acceptance Criteria:

Puppet should accept revision 3 task metadata, with a way to get absolute paths of files.

Team: Bolt
Sprint: Bolt Kanban
Release Notes: Bug Fix
Release Notes Summary: For Bolt: the task object returned by PAL's ScriptCompiler#task_signature method has been changed to pass through metadata to enable support for revision 3 of the task specification.
QA Risk Assessment: Needs Assessment

 Description   

Puppet's instantiation of a task - specifically what we get from PAL::ScriptCompiler#task_signature - should accept new metadata fields in https://github.com/puppetlabs/puppet-specifications/blob/master/tasks/task.json; specifically what the README documents as revision 3.

Additionally the task we get back should have a way to list the absolute paths of files referenced via the files properties of the task metadata.

Also look into removing Puppet's restriction on unknown metadata.



 Comments   
Comment by Michael Smith [ 2018/09/18 ]

Ideally we'd like to unify the separate validation for metadata from Module::Task and TaskInstantiator.

Generated at Fri Oct 18 02:38:04 PDT 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.