Uploaded image for project: 'MCollective'
  1. MCollective
  2. MCO-834

Mco -S command filtering on Structured Facts

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: MCO 2.12.2
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Bolt
    • Sprint:
      Bolt Kanban
    • CS Priority:
      Minor
    • CS Frequency:
      2 - 5-25% of Customers
    • CS Severity:
      3 - Serious
    • CS Business Value:
      2 - $$$
    • CS Impact:
      Hide
      It looks like there is some documentation about this in the release notes for mcollective, but having to read through this giant list to find them is suboptimal. These should be more clearly represented in the MCO usage docs.

      https://docs.puppetlabs.com/mcollective/releasenotes.html#structured-fact-support
      Show
      It looks like there is some documentation about this in the release notes for mcollective, but having to read through this giant list to find them is suboptimal. These should be more clearly represented in the MCO usage docs. https://docs.puppetlabs.com/mcollective/releasenotes.html#structured-fact-support
    • Release Notes:
      Not Needed
    • Release Notes Summary:
      Documentation update.

      Description

      There is absolutely no documentation besides the comment in this ticket, which doesn't even give the correct format to use: https://tickets.puppetlabs.com/browse/MCO-363

      A correct use can be shown here:
      peadmin@master:~$ mco ping -S 'fact("system_uptime.days").value=0'
      centos6a.pdx.puppetlabs.demo time=103.69 ms

      Note the need for double quotes around the fact which isn't in that comment.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              chris.matteson Chris Matteson
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support