No resource for service_name provider about octopus-deploy-cookbook HOT 6 CLOSED

I am not sure if I am following you correctly. You want the ability to specify a service name override. I am not sure if that makes sense since octopus deploy does not even allow you to change the name when you create instances of a tentacle. What does your resource block look like which is not working?

from octopus-deploy-cookbook.

In you providers.rb you have set the value "service_name = service_name(instance)". As an example this would name my tentacle service "OctopusDeploy Tentacle - WIN-NCHKE839". However, in our environment when the tentacles have been manually setup on the nodes the service name is only "OctopusDeploy Tentacle". This causes an issue when the recipe compiles and checks the not_if block "not_if { ::Win32::Service.exists?(service_name) }" specifically looking for "OctopusDeploy Tentacle - WIN-NCHKE839" which would evaluate as false although the tentacle service is already installed just with a slightly different name like "OctopusDeploy Tentacle". This causes any node that runs this recipe to error out due to the service name being slightly different than is prescribed in your providers.rb file.

from octopus-deploy-cookbook.

In the provider the instance is either passed in or defaulted. So the only way what you are saying could happen is if you did something like this.

octopus_deploy_tentacle 'default' do
  action [:install, :configure]
  instance 'WIN-NCHKE839'
  ...
end

In this example the instance name is being used to create multiple instances of the tentacle on the system. If there is a bug in how this works it would be beneficial to fix it. Currently we do not do that here which is why we haven't really had to go down that code path. If you only have one tentacle instance on the machine you are trying to install you should just not pass in the instance name.

from octopus-deploy-cookbook.

@jmcnair51 Does this answer your question or resolve the issue? If I dont' hear back I am going to close this issue.

from octopus-deploy-cookbook.

Sorry @brentm5 for the delayed response. Your suggestion did solve my issue, so thank you for your help. For lack of knowledge, I was under the impression that the instance name was a mandatory input. However, it is still possible to have both a service named OctopusDeploy Tentacle and OctopusDeploy Tentacle - Instance Name, so it would make it more flexible to be able to use a wildcard or explicitly define your service name. Thanks again and you can close this.

from octopus-deploy-cookbook.

No problem. Glad I could help!

from octopus-deploy-cookbook.