Jira (PUP-5600) Add "none" parameter to catalog_cache_terminus configuration reference

30 views
Skip to first unread message

Henrik Lindberg (JIRA)

unread,
May 16, 2017, 3:53:02 PM5/16/17
to puppe...@googlegroups.com
Henrik Lindberg updated an issue
 
Puppet / Improvement PUP-5600
Add "none" parameter to catalog_cache_terminus configuration reference
Change By: Henrik Lindberg
Labels: triaged
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Henrik Lindberg (JIRA)

unread,
May 16, 2017, 3:53:02 PM5/16/17
to puppe...@googlegroups.com

Henrik Lindberg (JIRA)

unread,
May 16, 2017, 3:54:02 PM5/16/17
to puppe...@googlegroups.com
Henrik Lindberg updated an issue

Moved to Agent. The setting is used on the agent side to cache a catalog.

Change By: Henrik Lindberg
Team: Puppet Developer Experience Agent

Josh Cooper (Jira)

unread,
May 18, 2020, 1:43:03 PM5/18/20
to puppe...@googlegroups.com
Josh Cooper commented on Improvement PUP-5600
 
Re: Add "none" parameter to catalog_cache_terminus configuration reference

This is no longer necessary because the agent doesn't update its cached catalog when running in noop mode, see PUP-10160. I'm going to close this ticket.

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

Charlie Sharpsteen (Jira)

unread,
May 18, 2020, 3:21:03 PM5/18/20
to puppe...@googlegroups.com

Josh Cooper PUP-10160 addresses --noop catalog getting unintentionally applied, but doesn't address the need to prevent Sensitive data from being written to disk. It is a bit of an edge case concern, but having the ability to toggle it off can save many hours of meetings and arguments with some auditors.

Josh Cooper (Jira)

unread,
May 18, 2020, 3:59:02 PM5/18/20
to puppe...@googlegroups.com
Josh Cooper commented on Improvement PUP-5600

Ah sorry Charlie Sharpsteen I missed your comment. Feel free to reopen if you think it'd be useful.

Charlie Sharpsteen (Jira)

unread,
Feb 27, 2023, 2:18:02 PM2/27/23
to puppe...@googlegroups.com

Re-opening this one as we just had another use case for skipping cache updates come in: Puppet agents that normally run with use_cached_catalog = true set in `puppet.conf`, but where Operators use Bolt tasks to roll out targeted updates by combining -no-use_cached_catalog with options like -tags that filter which parts of an upgrade catalog are enforced.

The problem is that -no-use_cached_catalog updates the cache, and the next regular scheduled daemon run enforces any remaining changes that were not filtered by -tags.

This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Atlassian logo

Charlie Sharpsteen (Jira)

unread,
Feb 27, 2023, 2:18:03 PM2/27/23
to puppe...@googlegroups.com
Charlie Sharpsteen updated an issue
 
Change By: Charlie Sharpsteen
Affects Version/s: PUP 6.28.0
Affects Version/s: PUP 7.23.0

Charmaine Pritchett (Jira)

unread,
Feb 27, 2023, 2:19:01 PM2/27/23
to puppe...@googlegroups.com

Charmaine Pritchett (Jira)

unread,
Feb 27, 2023, 2:19:02 PM2/27/23
to puppe...@googlegroups.com
Charmaine Pritchett updated an issue
Change By: Charmaine Pritchett
Zendesk Ticket Count: 1
Zendesk Ticket IDs: 50974

Charlie Sharpsteen (Jira)

unread,
Feb 28, 2023, 2:08:03 PM2/28/23
to puppe...@googlegroups.com
Charlie Sharpsteen updated an issue
Change By: Charlie Sharpsteen
Issue:
There is currently no "none' parameter to pass the catalog_cache_terminus reference. If you want your --noop run not to trigger changes from a cache catalog as in (PUP-3077) you currently have to pass an invalid string:

puppet agent -t --noop --catalog_cache_terminus=
`` ''

Request:
It would be nice to have the a "none" option similar to how you can specify "none" to disable data bindings in hiera (https://docs.puppetlabs.com/hiera/3.0/puppet.html#to-disable)

Tony Vu (Jira)

unread,
Feb 28, 2023, 4:53:01 PM2/28/23
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages