Jira (PUP-1043) Remove ability to specify file checksum in `content` property

Nicholas Fagerlund (JIRA)

unread,

May 15, 2017, 1:44:05 PM5/15/17

to puppe...@googlegroups.com

Nicholas Fagerlund updated an issue

Puppet /

PUP-1043

Remove ability to specify file checksum in `content` property

Change By:	Nicholas Fagerlund
Summary:	Deprecate and remove Remove ability to specify file checksum in `content` property

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

Nicholas Fagerlund (JIRA)

unread,

May 15, 2017, 1:46:04 PM5/15/17

to puppe...@googlegroups.com

Nicholas Fagerlund updated an issue

Puppet /

PUP-1043

Remove ability to specify file checksum in `content` property

Change By:	Nicholas Fagerlund

We added The {{checksum_value}} attribute is the co replacement for this use case (setting content => <md5 chucksum>), but you can still use magic {{content}} values. We have to remove this, but it needs to be on a major version boundary, probably Puppet 6.

---

Previous description:

Rather than passing around the contents of a file (e.g. in logs) we use the checksum; to support this the user is also allowed to _specify_ the contents as a checksum, but this leads to an ambiguity when the actual contents match the checksum pattern.

Instead of trying to do magic, we should have distinct syntax for referring to the contents by checksum (which should _always_ expect a valid checksum) and for specifying the contents literally (which shouldn't do anything different if the contents happen to resemble a checksum).

Add Comment

Moses Mendoza (JIRA)

unread,

May 18, 2017, 1:44:32 PM5/18/17

to puppe...@googlegroups.com

Moses Mendoza updated an issue

Puppet /

PUP-1043

Remove ability to specify file checksum in `content` property

Change By:	Moses Mendoza
Labels:	redmine triaged

Add Comment

Josh Cooper (JIRA)

unread,

Mar 19, 2018, 5:29:03 PM3/19/18

to puppe...@googlegroups.com

Josh Cooper updated an issue

Puppet /

PUP-1043

Remove ability to specify file checksum in `content` property

Change By:	Josh Cooper
Sub-team:	Coremunity

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Jacob Helwig (JIRA)

unread,

Mar 27, 2018, 4:55:04 PM3/27/18

to puppe...@googlegroups.com

Jacob Helwig updated an issue

Puppet /

PUP-1043

Remove ability to specify file checksum in `content` property

Change By:	Jacob Helwig
Sprint:	Platform Core Hopper

Add Comment

Jennifer Solman (JIRA)

unread,

Apr 24, 2018, 1:20:04 PM4/24/18

to puppe...@googlegroups.com

Jennifer Solman updated an issue

Puppet /

PUP-1043

Remove ability to specify file checksum in `content` property

Change By:	Jennifer Solman

The {{checksum_value}} Using the source attribute to access static catalogs is the replacement for this use case (setting content => <md5 chucksum>), but you can still use magic {{content}} values. We have to remove this, but it needs to be on a major version boundary, probably Puppet 6.

---

Please ensure consistency with the deprecation warning provided to users:

Using a checksum in a file\'s "content" property is deprecated. The ability to use a checksum to retrieve content from the filebucket using the "content" property will be removed in a future release. The literal value of the "content" property will be written to the file. Functionality is being replaced by the use of static catalogs. See https://puppet.com/docs/puppet/latest/static_catalogs.html for more information.

—

Previous description:

Rather than passing around the contents of a file (e.g. in logs) we use the checksum; to support this the user is also allowed to _specify_ the contents as a checksum, but this leads to an ambiguity when the actual contents match the checksum pattern.

Instead of trying to do magic, we should have distinct syntax for referring to the contents by checksum (which should _always_ expect a valid checksum) and for specifying the contents literally (which shouldn't do anything different if the contents happen to resemble a checksum).

Add Comment

Jennifer Solman (JIRA)

unread,

Apr 24, 2018, 1:20:06 PM4/24/18

to puppe...@googlegroups.com

Jennifer Solman updated an issue

Puppet /

PUP-1043

Remove ability to specify file checksum in `content` property

Change By:	Jennifer Solman

Using the source attribute to access static catalogs is the replacement for this use case (setting content => <md5 chucksum>), but you can still use magic {{content}} values. We have to remove this, but it needs to be on a major version boundary, probably Puppet 6.

Please ensure consistency with the deprecation warning provided to users:

Using a checksum in a file\'s "content" property is deprecated. The ability to use a checksum to retrieve content from the filebucket using the "content" property will be removed in a future release. The literal value of the "content" property will be written to the file. Functionality is being replaced by the use of static catalogs. See

[ https://puppet.com/docs/puppet/latest/static_catalogs.html ] for more information.

—

Previous description:

Rather than passing around the contents of a file (e.g. in logs) we use the checksum; to support this the user is also allowed to _specify_ the contents as a checksum, but this leads to an ambiguity when the actual contents match the checksum pattern.