Uploaded image for project: 'Facter'
  1. Facter
  2. FACT-1575

Add the ability to cache and block the output of custom facts

    XMLWordPrintable

Details

    • Hide
      • Custom Ruby facts can be cached via entries to the `ttls` config field
      • Custom Ruby facts can be blocked via entries to the `blocklist` config field
      • CLI options around caching and blocking take into account custom Ruby facts
      Show
      Custom Ruby facts can be cached via entries to the `ttls` config field Custom Ruby facts can be blocked via entries to the `blocklist` config field CLI options around caching and blocking take into account custom Ruby facts
    • Night's Watch
    • 3
    • NW - 2020-01-22, NW - 2020-02-05, NW - 2020-02-19, NW - 2020-03-04, NW - 2020-03-17, NW - 2020-04-01
    • Reviewed
    • New Feature
    • Hide
      Allows the user to cache custom facts based on facter.conf file.

      Custom facts defined in facter.conf under Facts.cached-custom-facts will be cached depending on the ttl defined under Facts.ttls.
      Show
      Allows the user to cache custom facts based on facter.conf file. Custom facts defined in facter.conf under Facts.cached-custom-facts will be cached depending on the ttl defined under Facts.ttls.
    • Needs Assessment

    Description

      In the first round of Configurable Facter work, we added the ability to cache and block built-in facts via settings in the config file. There is also demand to be able to cache and block custom Ruby facts. Blocking should be straightforward, but to implement caching, some updates to the methods dealing with the fact cache are needed, since they currently assume resolvers are the source of all the fact data.

      In order to keep the feel similar to resolvers, and in response to customer feedback, custom facts should specify a cache group in the form of a sort of tag in the fact, which can be used to cache or block any custom fact with that tag.

      In addition, the output of the list-block-groups and list-cache-groups command line options need to be updated to also report custom facts available for caching and blocking.

      Attachments

        Issue Links

          is cloned by

          New Feature - A new feature of the product, which has yet to be developed. FACT-2331 Add the ability to cache and block the output of custom facts

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Resolved
          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. FACT-1842 The ability to blocklist individual facts

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. PUP-9577 Large numbers of facts cause slow performance

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Accepted

          Task - A task that needs to be done. FACT-1472 Ensure the collection has enough information about external facts to cache them.

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. FACT-1858 Provide an option to disable legacy facts so they are not sent to the master from the agent

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Resolved

          Task - A task that needs to be done. FACT-1471 Ensure the Collection has enough information about Ruby facts to cache their output

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Resolved
          mentioned in

          Page Loading...

          Activity

            People

              dorin.pleava Dorin Pleava
              maggie Maggie Dreyer
              Votes:
              5 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support