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

write public information to puppet_dir/public

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 7.0.0
    • Component/s: None
    • Template:
    • Team:
      Night's Watch
    • Story Points:
      1
    • Sprint:
      NW - 2020-09-01, NW - 2020-09-16
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      A new folder named `public`, with 0755 access rights, has been added and is now the default location for the 'last_run_summary.yaml' report which now has `640` file permissions.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppet needs a new folder called `public` which should be accessible by everyone (public user class) and have the public puppet files such as last run summary (without sensitive data in them) stored there. Default location proposed is `/opt/puppetlabs/puppet/public` on Linux and `C:\ProgramData\PuppetLabs\puppet\public` on Microsoft Windows. Both the folder and containing files should have `0755` (rwxr-xr-x) permissions set. Installation/upgrade of puppet-agent should ensure the existence of this folder.

      Custom path for this folder should be possible through custom settings in `puppet.conf` or using the `puppet config set publicdir <custom_path>` cli command. Current implementation should only include the `last_run_summary.yaml` file in said folder (which is currently located in `/opt/puppetlabs/puppet/cache/state` on Linux and `C:\ProgramData\PuppetLabs\puppet\cache\state` on Microsoft Windows).

      Changes needed in Puppet Agent (regarding the new cli parameter setting and folder packaging) should be covered in PA-3253.

        Attachments

          Activity

            People

            Assignee:
            luchian.nemes Luchian Nemes
            Reporter:
            mihai.buzgau Mihai Buzgau
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support