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

Re-implement `puppet facts upload` and associated server endpoint



    • Epic
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • PUP 5.5.0
    • None
    • Re-enable `puppet facts upload`
    • Platform Core
    • Major
    • 4 - 50-90% of Customers
    • 3 - Serious
    • 5 - $$$$$$
    • Having fresh facts is only going to become higher priority as tasks become more popular and users get more experience with PQL for targeting them. This is also a big enabler of the direct puppet workflow.
    • Not Needed
    • Needs Assessment


      In PUP-1874 and PUP-2560 we unwisely removed a useful bit of functionality: the ability to upload facts to the master independent of catalog request. The implementation talked to a deprecated API, and what we should have done was to improve the server API, not remove the functionality completely. Users find this extremely useful (see PUP-5934) and it's an important stepping stone on the road to asynchronous catalog compilation in Direct Puppet.

      This ticket should track the re-implementation of this functionality. There are two parts:
      1. a command line executable which, when run, gathers facts and uploads them to the puppet master
      2. an endpoint on the puppet-server which receives the facts and submits them to PuppetDB. This endpoint should be subject to tk-auth rules that permit a node to replace its own facts. (The documented workaround of having endpoints upload their facts directly to puppetdb is unsuitable because most sites do not expose the puppetdb API to endpoints at all.)


        Issue Links



              chuck Charlie Sharpsteen
              eric.sorenson Eric Sorenson
              6 Vote for this issue
              23 Start watching this issue



                Zendesk Support