Uploaded image for project: 'Puppet Task Runner'
  1. Puppet Task Runner
  2. BOLT-330

Users should be able to use wildcards to target nodes in inventory

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: BOLT 0.16.2
    • Component/s: None
    • Labels:
      None
    • Template:
    • Epic Link:
    • Sprint:
      Bolt Kanban
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      You can refer to nodes enumerated in inventory using the '*' wild card. For example `puppet task run minifact --nodes 'foo*.example.com'`. Note that in most shells, the wildcard will need to be quoted or escaped to avoid shell expansion.

      This makes sense to add to the section at https://puppet.com/docs/bolt/0.x/bolt_options.html#specifying-nodes
      Show
      You can refer to nodes enumerated in inventory using the '*' wild card. For example `puppet task run minifact --nodes 'foo*.example.com'`. Note that in most shells, the wildcard will need to be quoted or escaped to avoid shell expansion. This makes sense to add to the section at https://puppet.com/docs/bolt/0.x/bolt_options.html#specifying-nodes
    • QA Risk Assessment:
      Needs Assessment

      Description

      If users have listed nodes in their inventory file they should be able to run against them with wild card statements like:

      foo-*.example.com

      Questions:
      should users define groups instead perhaps? (probably not)
      What should the syntax be? x*y -> /^x.*y$/
      Should users be able to use wildcards with groups? no
      If a wildcard is present but no nodes match, should we try to use it as a target name (and probably error), error immediately, or return an empty list? Fail immediately if no nodes match.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  alex Alex Dreyer
                  Reporter:
                  alex Alex Dreyer
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: