Jira (PUP-3613) Add a parameter to the exec resource to support running commands in software collections without always using "scl enable"

2017-05-18 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3613 
 
 
 
  Add a parameter to the exec resource to support running commands in software collections without always using "scl enable"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Labels:
 
 redmine  triaged 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3613) Add a parameter to the exec resource to support running commands in software collections without always using "scl enable"

2017-05-15 Thread Sean McDonald (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3613 
 
 
 
  Add a parameter to the exec resource to support running commands in software collections without always using "scl enable"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean McDonald 
 
 
 

Labels:
 
 redmine  triaged 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3613) Add a parameter to the exec resource to support running commands in software collections without always using scl enable

2015-07-07 Thread Stefan Lasiewski (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Lasiewski updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3613 
 
 
 
  Add a parameter to the exec resource to support running commands in software collections without always using scl enable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stefan Lasiewski 
 
 
 
 
 
 
 
 
 
 SoftwarecollectionsisanRPMintegratedvendorizationtoolthat'sstartingtogetmoreandmorewidelyused+supported.Torunacommandinthesoftwarecollection(SCL),youneedtorun`sclenablecollectionname'command'`.Forexample,ifyouwanttoinstallagemintoaSCLnamedruby193,you'drun`sclenableruby193'/usr/bin/geminstallsinatra'`.Here'swhatI'mproposing: pre {code} exec{'installsinatra':command='/usr/bin/geminstallsinatra',unless='gemlist|grepsinatra',scl='ruby193'} /pre {code} ThepresenceoftheSCLparametermeansthatalloftheotherparametersthatinvolvesystemcallswouldgetexecutedinsideofasessionintheSCLnamethat'sprovided. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3613) Add a parameter to the exec resource to support running commands in software collections without always using scl enable

2015-04-16 Thread Tim Skirvin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tim Skirvin commented on  PUP-3613 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add a parameter to the exec resource to support running commands in software collections without always using scl enable  
 
 
 
 
 
 
 
 
 
 
It is important for those of us developing puppet modules on RHEL and other RedHat systems to be able to use the standard ruby tool suite for our work - e.g. rspec-puppet, beaker, etc. But RedHat is still using ruby 1.8.7 by default (and probably will be for years to come).  
This new feature would improve matters dramatically for us poor RHEL users. 
Note that I am currently writing a little 'ruby193::gem' definition just to work around this problem locally. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3613) Add a parameter to the exec resource to support running commands in software collections without always using scl enable

2014-11-06 Thread Charlie Sharpsteen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Charlie Sharpsteen commented on  PUP-3613 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add a parameter to the exec resource to support running commands in software collections without always using scl enable  
 
 
 
 
 
 
 
 
 
 
This would require a non-trivial amount of build out in code, tests, debugging info, etc. to support a RHEL-specific option for a very universal and heavily-used type. There would be ongoing costs in terms of bugs and manintenance. I'm not convinced there is a good trade-off in favor of this feature given that this use case is supported by pre-pending three words, scl enable foo, to a command. Four a large numbers of commands, the overhead of setting and updating this could be reduced by using variables. 
As a user and debugger of puppet code, I'd rather see this context explicitly inline with the command rather than having to hunt through manuals and resource defaults in order to figure out what is getting run. 
Any use cases that would justify the cost and complexity of implementing this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3613) Add a parameter to the exec resource to support running commands in software collections without always using scl enable

2014-11-04 Thread redmine.exporter (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 redmine.exporter created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3613 
 
 
 
  Add a parameter to the exec resource to support running commands in software collections without always using scl enable  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2014/11/04 5:28 AM 
 
 
 

Labels:
 

 redmine 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 redmine.exporter 
 
 
 
 
 
 
 
 
 
 
Software collections is an RPM integrated vendorization tool that's starting to get more and more widely used + supported. To run a command in the software collection (SCL), you need to run `scl enable collection name 'command'`. For example, if you want to install a gem into a SCL named ruby193, you'd run `scl enable ruby193 '/usr/bin/gem install sinatra'`. Here's what I'm proposing: 
pre exec  { 'install sinatra': command = '/usr/bin/gem install sinatra', unless = 'gem list | grep sinatra', scl = 'ruby193' } 
/pre 
The presence of the SCL parameter means that all of the other parameters that involve system calls would get executed inside of a session in the SCL name that's provided.