Jira (PUP-1098) Package/source should accept puppet:// files

Rob Nelson (JIRA)

unread,

Dec 4, 2014, 3:51:29 PM12/4/14

to puppe...@googlegroups.com

Rob Nelson commented on

PUP-1098

Re: Package/source should accept puppet:// files

Redmine #4074 and #11865 seem to agree that this is needed but have a weird circular reference where each says to see the other. Charlie, I'm not sure who this should be assigned to, could you help determine who can make the decision on this?

Add Comment

This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)

Rob Nelson (JIRA)

unread,

Dec 4, 2014, 3:51:29 PM12/4/14

to puppe...@googlegroups.com

Rob Nelson updated an issue

Puppet /

PUP-1098

Package/source should accept puppet:// files

Change By:	Rob Nelson
Assignee:	Charlie Sharpsteen

Add Comment

Charlie Sharpsteen (JIRA)

unread,

Jun 8, 2016, 5:49:04 PM6/8/16

to puppe...@googlegroups.com

Charlie Sharpsteen assigned an issue to Unassigned

Puppet /

PUP-1098

Package/source should accept puppet:// files

Change By:	Charlie Sharpsteen
Assignee:	Charlie Sharpsteen

Add Comment

This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Henrik Lindberg (JIRA)

unread,

Jun 8, 2016, 6:12:06 PM6/8/16

to puppe...@googlegroups.com

Henrik Lindberg updated an issue

Puppet /

PUP-1098

Package/source should accept puppet:// files

Ping Kylo Ginsberg

Change By:	Henrik Lindberg
Scrum Team:	Client Platform

Add Comment

Patrik Svensson (JIRA)

unread,

Jun 22, 2016, 8:48:04 AM6/22/16

to puppe...@googlegroups.com

Patrik Svensson commented on

PUP-1098

Re: Package/source should accept puppet:// files

This would be incredible useful on Windows.

Add Comment

Eric Sorenson (JIRA)

unread,

Jul 13, 2016, 6:30:03 PM7/13/16

to puppe...@googlegroups.com

Eric Sorenson updated an issue

Puppet /

PUP-1098

Package/source should accept puppet:// files

Change By:	Eric Sorenson

Sometimes you need to use backported packages on debian-like system (we could easily imagine use cases for other platforms). In work/production environments, it's quite rare to have directly access to the Internet for security reasons. So "package" type should accept a "source" located on the puppet master filebucket file server , whereas it only accepts local packages for the moment.

Said differently, I'd like to turn this kind of awful recipe : {code}
class apache2-passenger {
  package {"libapache2-mod-passenger":
    ensure => installed,
    provider => dpkg,
    source => "/tmp/mod-passenger.deb"
    require => File[tmp-passenger]
  }
  file {"tmp-passenger":
    name => "/tmp/mod-passenger.deb",
    owner => root,
    group => root,
    source => "puppet:///files/redmine/libapache2-mod-passenger_2.2.11debian-1~bpo50+1_i386.deb"
  }
}
{code}
Into something like this :
{code}
class apache2-passenger {
  package {"libapache2-mod-passenger":
    ensure => installed,
    provider => dpkg,
    source => "puppet:///files/passenger/libapache2-mod-passenger_2.2.11debian-1~bpo50+1_i386.deb"
  }
}
{code}
Let me know your opinion about that. Thanks!