Issue #6599 has been updated by Nigel Kersten. Project changed from Product Roadmap to Puppet Category deleted (Puppet) Parent task deleted (#6598)
---------------------------------------- Feature #6599: The client should default to using its cached catalog https://projects.puppetlabs.com/issues/6599 Author: Luke Kanies Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: We currently default to the client upgrading its catalog every time, and there's no straightforward mechanism to change this default. This means that all phased roll-out work must involve working directly on the clients to control catalog updates. We should instead switch to a model where the client can ask the server if it should update its catalog, and by default uses its existing catalog. This should probably be done by the client sending the server its catalog version and the server returning a boolean on whether it should be retrieving a new catalog. Alternatively, it could do something like a 'HEAD' request on a new catalog and compare the versions on the client, and decide to upgrade based on that. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
