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

Deprecate source_permissions

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 5.5.6
    • Component/s: Docs
    • Labels:
    • Template:
      PUP Bug Template
    • Acceptance Criteria:
      Hide

      We should emit a deprecation warning if anyone puts "source_permissions" in their manifests. We should not emit a deprecation warning during pluginsync (when we programmatically create a catalog with a file resource).

      We should be communicating via docs or some other method for migration implications from 3.x

      Show
      We should emit a deprecation warning if anyone puts "source_permissions" in their manifests. We should not emit a deprecation warning during pluginsync (when we programmatically create a catalog with a file resource). We should be communicating via docs or some other method for migration implications from 3.x
    • Team:
      Coremunity
    • Sprint:
      Platform Core KANBAN
    • Release Notes:
      Deprecation
    • Release Notes Summary:
      Setting source_permissions to use or use_when_creating is deprecated. If permissions should be managed, set them explicitly using owner, group, mode.

      Description

      We are steering people away from source_permissions for two reasons:

      1. it doesn't make sense for environments (including PE) that use git for the backend (user/group aren't managed by git)
      2. it is not fully supported/supportable by static_catalogs no longer true, it will now be fully supported in static_catalogs

      It is still used by pluginsync for external facts however, and we will need to find a replacement mechanism for that, see linked PUP-5920.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kris.bosland Kris Bosland
              Reporter:
              kylo Kylo Ginsberg
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support