Jira (PUP-3525) Puppetmaster needs a RESTful way to flush environment caches

[Eric Sorenson (JIRA)]

Title: Message Title

Eric Sorenson created an issue   Puppet / PUP-3525 Puppetmaster needs a RESTful way to flush environment caches Issue Type: New Feature Assignee: Unassigned Created: 23/Oct/14 5:09 PM Priority: Normal Reporter: Eric Sorenson Users are experiencing problems with changes they make to Puppet modules on the filesystem not showing up immediately, either from catalog compilation or other endpoints like ''resource_types". We're moving towards a world where the environment_timeout is really a bi-state setting: either "I'm in a constantly-changing dev environment, don't cache at all" or "I'm running in production, cache forever until I deploy new code", but we're not quite at the point where the latter use-case is done end-to-end. All of that is prelude to saying, it would be greatly helpful to have a REST action that could cause a master to expire all of its environment caches so subsequent hits for catalogs, resource_types, etc go to the filesystem. The user would knowingly incur the performance penalty because they know they're getting stale data and want it to be fresh. Add Comment   This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.