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

Formalize Types and Providers API

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Epic Name:
      Types and Providers API
    • Template:
    • Team/s:
      Coremunity

      Description

      First, a caveat: this is probably more like a meta-epic and we should treat this as a living ticket, breaking it out into other epics (or dismantling it entirely) if appropriate.

      With that out of the way: this is intended to capture activity and ideas around how to formalize the types and providers API. It's hard to imagine this wouldn't ultimately involve some deprecations of understood behavior as well as some discoveries of implicit/accidental behavior.

      For now, it would be useful to use this epic to capture some of the miscellaneous tickets requesting enhancements and/or bug fixes affecting the current types and providers API. Part of my thought is that capturing such tickets under one epic will further discussion of a well-considered solution balancing tradeoffs between different requirements and use cases.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            kylo Kylo Ginsberg
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support