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

Make executing each component config driven #18

Open
1 of 2 tasks
majormoses opened this issue Mar 21, 2018 · 2 comments
Open
1 of 2 tasks

Make executing each component config driven #18

majormoses opened this issue Mar 21, 2018 · 2 comments

Comments

@majormoses
Copy link
Collaborator

majormoses commented Mar 21, 2018

I think there is value in being able to use this tool even without sensu or chef, I'd like to propose we only run each component if the config specifies we should. To avoid a breaking change we could default to still considering sensu and chef default but allow explicit disabling. If this sounds good I will create a PR when I have some time.

EDIT: adding checklist

  • sensu
  • chef
@eheydrick
Copy link
Owner

I think that would be good. Have an enable boolean on chef, sensu, etc like there is on the chat options.

@majormoses majormoses changed the title Make removing from each component config driven Make executing each component config driven Mar 22, 2018
@majormoses
Copy link
Collaborator Author

Ya that was my thought, I am gonna work on doing this just for sensu right now as chef is currently very tightly coupled and all my current use cases involve chef even if not sensu. When someone wants to add support for another CM tool we can use that opportunity to add the same for chef.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants