Jira (PUP-6939) New users are confused by package's ensure=>$version

[David Schmitt (JIRA)]

David Schmitt created an issue

Puppet / PUP-6939 New users are confused by package's ensure=>$version Issue Type: Story Assignee: Unassigned Components: Types and Providers Created: 2016/11/24 3:06 AM Priority: Normal Reporter: David Schmitt As a new user looking at package resources The lack of a "version" property is confusing. This was found by the Next-Gen team during review. Add Comment

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

[David Schmitt (JIRA)]

David Schmitt commented on PUP-6939

Re: New users are confused by package's ensure=>$version This will require a long-term migration to a) provide the version property as an alternative to specifying the version in the ensure b) once this is available to "many" users, start complaining about version strings in ensure in puppet-lint c) once this is available to "most" users, start deprecating version strings in ensure at runtime d) once "most" deprecations are addressed, remove the original functionality in the next major puppet version

Add Comment

[Matthew Thode (JIRA)]

Matthew Thode commented on PUP-6939

Re: New users are confused by package's ensure=>$version

This would also allow us to remove specific versions of versionable packages. see https://projects.puppetlabs.com/issues/2061 for the old discussion.

Add Comment

[Matthew Thode (JIRA)]

Matthew Thode commented on PUP-6939

Re: New users are confused by package's ensure=>$version

You could actually overload the package name instead. 1. providers learn how to parse package names based on their package naming guidelines 2. warn about version strings in `ensure` 3. once this is available to "most" users, start deprecating version strings in ensure at runtime 4. once "most" deprecations are addressed, remove the original functionality in the next major puppet version Basically the same, but without a new property.

Add Comment

[Matthew Thode (JIRA)]

Matthew Thode commented on PUP-6939

Re: New users are confused by package's ensure=>$version

An example of this is https://gist.github.com/80860761d3f523b4e19fa2e99c96e613 (didn't see a way to upload) specifically for gentoo the qatom binary allows us to parse package names

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Puppet / PUP-6939

New users are confused by package's ensure=>$version

Change By: Maggie Dreyer Labels: needs_decision

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Puppet / PUP-6939 New users are confused by package's ensure=>$version

Change By: Maggie Dreyer Labels: needs_decision  triaged

Add Comment

[Moses Mendoza (JIRA)]

Moses Mendoza updated an issue

Puppet / PUP-6939 New users are confused by package's ensure=>$version

Change By: Moses Mendoza Team: Agent

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Puppet / PUP-6939 New users are confused by package's ensure=>$version

Change By: Branan Riley Labels: beaking future needs_decision package triaged type_and_provider

Add Comment

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

[Branan Riley (JIRA)]

Branan Riley updated an issue

Puppet / PUP-6939 New users are confused by package's ensure=>$version

Change By: Branan Riley Labels: beaking breaking future needs_decision package triaged type_and_provider

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-6939

Re: New users are confused by package's ensure=>$version We're unlikely to deprecate specifying version strings in the package ensure property as this would literally cause issues for every puppet user. Closing this.

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)