Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-9153

Puppet Task metadata should support task spec revision 3

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 6.0.1
    • Component/s: None
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide

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

      Show
      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.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            michael.smith Michael Smith
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support