Jira (PUP-7779) Re-implement `puppet facts upload` and associated server endpoint

[Eric Sorenson (JIRA)]

Title: Message Title

Eric Sorenson created an issue   Puppet / PUP-7779 Re-implement `puppet facts upload` and associated server endpoint Issue Type: Epic Assignee: Unassigned Created: 2017/07/14 2:03 PM Priority: Normal Reporter: Eric Sorenson 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.) Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.