Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-6372

SPIKE: Determine if v1 scheduled task type / provider should be reinstated in module OR unavailable for Puppet 6

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: scheduled_task
    • Labels:
    • Template:
    • Acceptance Criteria:
      Hide

      The implied end goal is to be able to use existing code unmodified with Puppet 6 + this module.

      Show
      The implied end goal is to be able to use existing code unmodified with Puppet 6 + this module.
    • Team:
      Windows
    • Sprint:
      Windows 2019-02-20
    • QA Risk Assessment:
      Needs Assessment

      Description

      With Puppet 6, the scheduled_task type and provider are being removed completely.

      The new scheduled_task module has a v2 specific type and provider that contains new functionality and deviates from the v1 type definition. We've already decided that to opt into newer v2 behavior, we require that a new type be used. However, to use the new provider with the existing type has required modification to manifests to opt-in to using the newer provider.

      With the removal of the v1 type, users would have to modify manifests to change providers explicitly OR we have to change the default provider for the v1 type. To do this requires reinstating the v1 type somewhere - which makes the most sense in this module.

      It's also possible that we leave a completely intact backwards compatible v1 type / provider in this module so that users are not required to make any manifest changes.

      The key here is not requiring users to modify code if they don't have to... the details of which will be investigated as part of this ticket.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            ethan Ethan Brown
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support