Jira (BOLT-1539) Local fact-cache functionality

[Mike Smith (Jira)]

Mike Smith created an issue

Puppet Task Runner / BOLT-1539 Local fact-cache functionality Issue Type: New Feature Assignee: Unassigned Created: 2020/03/07 11:27 AM Labels: bolt Priority: Normal Reporter: Mike Smith In various scenarios a user would have a potential target base of enough servers that they would need to arbitrarily filter them for running commands/scripts/tasks/plans.  These facts could be used to either filter runs, inform logic, or provide data.  An example of this in the Ansible feature set is fact-caching - [here is a blog|https://jpmens.net/2015/01/29/caching-facts-in-ansible/] that provides an end-to-end example.  This feature was discussed in a Bolt workshop where the room was heavily Ansible users.  In scenarios where PuppetDB is setup and accessible this would account for the above need. In various Puppet open source or enterprise deployments not all potential targets have Puppet agents nor do all users have access to PuppetDB.     Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Mike Smith (Jira)]

Mike Smith updated an issue

Puppet Task Runner / BOLT-1539 Local fact-cache functionality

Change By: Mike Smith CS Priority: Needs Priority

Add Comment

[Mike Smith (Jira)]

Mike Smith updated an issue

Puppet Task Runner / BOLT-1539 Local fact-cache functionality Change By: Mike Smith

In various scenarios a user would have a potential target base of enough servers that they would need to arbitrarily filter them for running commands/scripts/tasks/plans.  These facts could be used to either filter runs, inform logic, or provide data.  An example of this in the Ansible feature set is fact-caching - [here is a blog|[https://jpmens.net/2015/01/29/caching-facts-in-ansible/]] that provides an end-to-end example.  This feature was discussed in a Bolt workshop where the room was heavily Ansible users.  In scenarios where PuppetDB is setup and accessible this would account for the above need. In various Puppet open source or enterprise deployments not all potential targets have Puppet agents nor do all users have access to PuppetDB.

This was brought up during a Bolt workshop at Walmart with mostly Ansible users.

Add Comment

[Ryan RussellYates (Jira)]

Ryan RussellYates commented on BOLT-1539

Re: Local fact-cache functionality Users are highly unlikely to be able to ping PuppetDB directly from a Network Architecture standpoint.   Add in self-service, and there's almost no chance we're opening that up to "All IT Practitioners in my giant organization"   We're going to need some models that allow this information to be captured, exported and utilized in a sane way. Not all customers will need it, but for some it will be imperative for them to get this data and utilize it.

Add Comment

[Jarret Lavallee (Jira)]

Jarret Lavallee updated an issue

Puppet Task Runner / BOLT-1539 Local fact-cache functionality

Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed

Add Comment