date:20171103

Jira (PUP-8089) Pluginsync locale files

2017-11-03 Thread Maggie Dreyer (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  PUP-8089 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pluginsync locale files  
 
 
 
 
 
 
 
 
 
 
Merged to 5.3.x at https://github.com/puppetlabs/puppet/commit/c04f34256e3d0fe0d78390789d0bdeb4317a720f 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-1277) service does not implement custom start / stop commands on windows

2017-11-03 Thread Eric Sorenson (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  PUP-1277 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: service does not implement custom start / stop commands on windows  
 
 
 
 
 
 
 
 
 
 
If you want to use your own start/stop commands you need to specify the base service provider. 
 
 
 
 
 
 
service {'gitlab-runner': 
 
 
 
 
  ensure => stopped, 
 
 
 
 
  provider => base, 
 
 
 
 
  start => 'c:\windows\system32\windowspowershell\v1.0\powershell.exe Start-Service gitlab-runner', 
 
 
 
 
  stop => 'c:\windows\system32\windowspowershell\v1.0\powershell.exe Start-Service gitlab-runner', 
 
 
 
 
}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-1277) service does not implement custom start / stop commands on windows

2017-11-03 Thread Eric Sorenson (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1277 
 
 
 
  service does not implement custom start / stop commands on windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 
 
 
 
 
 
 
 The provider for service does not have support for explicit start and stop commands, however the documentation does not mention that limitation.Example (taken from the mcollective module): < { code > }   service { $mc_service_name:ensure=> running,enable=> true,hasstatus => true,start => $mc_service_start,stop  => $mc_service_stop,  }  { code > } Windows will still run the default command, which is:* C:\Windows\System32\net.exe $mc_service_name start* C:\Windows\System32\net.exe $mc_service_name stopIn stead of the specified start and stop commands.The fix could be a simple as this: < { code > } --- lib\puppet\provider\service\windows-orig.rb 2013-06-17 17:23:16 +0200+++ lib\puppet\provider\service\windows.rb 2013-10-25 11:57:42 +0200@@ -73,13 +73,21 @@   end end -net(:start, @resource[:name])+if @resource[:start]+  system(@resource[:start])+else+  net(:start, @resource[:name])+ end   rescue Puppet::ExecutionFailure => detail raise Puppet::Error.new("Cannot start #{@resource[:name]}, error was: #{detail}" )   enddef stop-net(:stop, @resource[:name])+if @resource[:stop]+  system(@resource[:stop])+else+  net(:stop, @resource[:name])+ end   rescue Puppet::ExecutionFailure => detail raise Puppet::Error.new("Cannot stop #{@resource[:name]}, error was: #{detail}" )   end  { code > } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)

Jira (BOLT-116) Consider the contents and format of a possible bolt.conf

2017-11-03 Thread Nathan Shobe (JIRA)

Title: Message Title

Nathan Shobe commented on BOLT-116

Re: Consider the contents and format of a possible bolt.conf

Obviously, core puppet devs can and will ultimately decide the direction bolt goes, but I'm going based upon the way people use the other "agentless" (which is a bad term) tool on the market. People general start projects using that tool in their small corner of a company/org/group and share their work, and it slowly expands from there. I just want to emphasize that the conf for bolt shouldn't rely on an existing puppet installation or infrastructure. People should be able to use this regardless of puppet agent adoption in a group of hosts and is why (from what I understand) the examples focus heavily on getting other languages to run.
And actually, as I'm writing this I'm starting to think that as long as I can run it with the data in module approach without requiring the environment or gobal layer it likely shouldn't impede adoption efforts.

Add Comment

This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)

--
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.

48 matches

Mail list logo