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

allow mode changes on files without restarting the service.

    Details

    • Type: New Feature
    • Status: Needs Information
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Template:

      Description

      I managed to have a booboo tonight by restarting a process which really shouldn't be. What I ran into was that a mode change caused subscribe to fire and the process to restart. Also given that "replace" only affects file contents, this means that you can never, ever change the mode of a file for new installs only, either. So it's always a risk of restarting a process.

      I think it's perfectly reasonable to want that subscribe/notify only fire on content changes. Also replace should maybe be expanded to also support giving
      other properties the same treatment perhaps? Not sure.

      I have thought and thought and I just can't find a situation where I think that changing the mode should cause a refresh. Owner or group in some circumstances, but not many. I think that the default should be content only, with an option to say "any attribute".

      RIP said: Lots of daemons ship files like accessible only by $daemon:$daemon when what we need is $daemon:$otherdaemon or maybe $daemon:$group_of_daemons. You want to notice $otherdaemon that it can now read that file etc

      So I think this argues that we should have an option for what changes invoke a refresh. Something like

           refreshon => 'content',
      

      or

           refreshon => ['owner','content'],
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                eric.sorenson Eric Sorenson
                Reporter:
                jorhett Jo Rhett
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Zendesk Support