[chef] Re: RE: Modifying Windows Service Logon As

[Kamil Markowicz < >]

I have not attempted to create an LWRP yet - I was trying to see if this is what I needed to do, as I was a little lost in the jargon of resources, providers, and LWRP's. The issue for me is lack of more than cursory knowledge of Ruby, so I have to work with a Ruby developer colleague on this :). I was just trying to get an idea of what we need to look for.

Maybe we'll stop by chef-dev soon - the name made me think it was for core chef development only.

Thanks for your guidance on this.

Kamil Markowicz
+1 312.970.9730

On Mon, Jan 6, 2014 at 3:23 PM, Adam Edwards < " target="_blank"> > wrote:

Kamil, I see you’ve opened a ticket on this: https://tickets.opscode.com/browse/CHEF-4921 so it can be triaged – thank you. the scenario is common enough that it seems like something that could go into the service resource in Chef itself.

 

Since there’s already an existing service resource and provider Kamil, you could try to reuse them in the short-term until Chef natively supports these the way you need, overriding the enable_service method of Chef::Provider::Service::Windows and adding attributes such as logon_as_user as you specified below.

 

Have you ever developed a lightweight resource provider before Kamil? If not, we can move over to chef-dev. These docs talk about what you can do to implement your own resource provider: http://docs.opscode.com/lwrp_custom_provider_ruby.html.

 

-Adam

 

From: " target="_blank"> [ " target="_blank">mailto: ] On Behalf Of Kamil Markowicz
Sent: Friday, January 3, 2014 9:47 AM
To: " target="_blank">
Subject: [chef] Modifying Windows Service Logon As

 

Hello Chefs,

 

We are currently evaluating Chef as a management tool for our Windows platform. We are playing around with some of the built in resources, and it did not take long to realize that crucial features are missing.

 

One of the items that is important to us is manipulating Windows services, specifically, the "Log On As" parameter. We need to be able to run Windows services under various (local and AD-authenticated) accounts.

 

We would prefer to have an abstracted way of doing this (i.e. not defining custom CMD/Powershell for each recipe that manipulates a service), for example by having logonas_user/logonas_password attributes for the service resource.

 

What documentation topics should we look at? Ideally, we'd like to somehow extend the existing Service resource (provider?). Should we look at developing a custom resource?

 

I am still somewhat intimidated some of the terminology, so I'd appreciate some pointers to the documentation or maybe examples of others doing similar work.

 

Thanks for your tips,

- Kamil