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

Prefer but don't require capabilities matching the node environment

    Details

    • Type: Task
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.8.0
    • Component/s: None
    • Labels:
    • Template:
    • Sub-team:
    • Team:
      Organizational Scale
    • Story Points:
      2
    • Sprint:
      HA - 2016-11-01, FF 2016-10-19
    • Release Notes:
      New Feature
    • Release Notes Summary:
      This allows application components to consume capabilities from other environments. If multiple capabilities are found the capability from the current environment will be preferred.

      Description

      Currently, capabilities are looked up strictly by environment. If the capability hasn't been produced in the same environment as the node, it will fail.

      That behavior disallows some branching workflows whereby some but not all nodes of an application may run in a different environment (ie. a topic branch). In that case, nodes will fail because the capabilities they depend on don't exist in their environment.

      To support that case, we should instead treat environment similar to code id. If there is one instance of a capability, use it regardless of its environment. If there are multiple instances of a capability, choose the one from the environment we're currently compiling in. If there are multiple instances and none matches the current environment, fail.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                nick Nick Lewis
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: