Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #262 for Windows #268

Closed
wants to merge 4 commits into from
Closed

Fixes #262 for Windows #268

wants to merge 4 commits into from

Conversation

Ginja
Copy link
Contributor

@Ginja Ginja commented Jan 28, 2016

It appears the nssm resource also isn't idempotent. I also added another
attribute and made it the default value for the install_path property for
consul_service. My reasoning is that one should be able to change this
crucial property without having to redeclare the whole resource. #262 will
be fixed for linux once
johnbellone/libartifact-cookbook#2 is merged

You can now remove previously set nssm parameters by setting the hash
values to '' for Strings, & 0 for Integers. Also improved how the
Consul service is stopped on Windows. If you don't stop it before
you remove it, you end up in a SERVICE_PAUSED state.
If nssm reported SERVICE_PAUSED for the consul service, the nssm
resource was unable to remove it. Altered the service status check
so it's flexible to handle multiple exit statuses.
It appears the nssm resource also isn't idempotent. I also added
another attribute and made it the default value for the install_path
property for consul_service. My reasoning is that one should be able
to change this crucial property without having to redeclare the whole
resource. #262 will be fixed for linux once
johnbellone/libartifact-cookbook#2 is merged
@Ginja Ginja closed this Jan 28, 2016
@Ginja Ginja deleted the fixes-idempotency branch January 28, 2016 21:51
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant