[PUP-5921] Deprecate source_permissions - Puppet Jira Server

XML

Word

Printable

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
Epic Link:
Puppet 5.y Deprecations
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.

We are steering people away from source_permissions for two reasons:

it doesn't make sense for environments (including PE) that use git for the backend (user/group aren't managed by git)
~~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~~.

causes

MODULES-7791 The pe_repo and puppet_agent modules should not use file.source_permissions in 2019.0.x

relates to

PUP-9332 deprecation message about source_permissions parameter with file resource

PUP-7534 Deprecate using file checksums in `content` property

PUP-5920 Implement pluginsync of external facts without using source_permissions