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

classes should be allowable as application components

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.3.0
    • Component/s: Language
    • Labels:
      None
    • Release Notes:
      Not Needed
    • Release Notes Summary:
      Part of new feature

      Description

      Currently, only defined resource types are allowed as components declared within an application{} model.

      Puppet classes, specifically the resource-syntax style of class declarations, should be allowable as application components.

      The primary difference in behavior for our purposes is that classes declared in this way are intended to be singleton. It can only be declared once on a given node. So, we'll need some error-handling affordances when the user tries to declare a given component in more than one application that are instantiated on the same Puppet node.

      This will be useful for many existing Forge modules which are modeled in classes, not defined resource types. One use case that comes to mind is a database server that may be modeled as part of a database service for the infrastructure but can only be declared once on a node.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                john.duarte John Duarte
                Reporter:
                ryan Ryan Coleman
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support