Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-2702

Change environment_timeout default to unlimited

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Modules
    • Labels:
    • Template:
    • Story Points:
      1
    • Sprint:
      Week 2014-5-28 to 2014-6-4

      Description

      UPDATED

      After yet more discussions (see original below). The decision was reverted in PUP-4094. The decision was to use 0 (no caching) as this provides the least surprising effect when using puppet "out of the box".

      ORIGINAL


      After a lot of discussion (see PUP-2639) we agreed that the correct default for puppet's environment caching is unlimited. This is because it is the correct thing to do in a production system where deployments of new code should be a controlled affair. Require the master to reload itself for a code deploy also gets around any problems it might have for any loaded ruby code.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              andy Andrew Parker
              QA Contact:
              Kurt Wall
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support