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

Drop enforcement that anomaly.detection.goals must be a subset of self.healing.goals (if non-empty). #1500

Closed
efeg opened this issue Mar 25, 2021 · 0 comments · Fixed by #1501
Assignees
Labels
correctness A condition affecting the proper functionality.

Comments

@efeg
Copy link
Collaborator

efeg commented Mar 25, 2021

Currently when a user attempts to explicitly set a self.healing.goals config that is not a superset of anomaly.detection.goals, there is a sanity check that causes CC to fail deployment with the error message:

Attempt to configure anomaly detection goals as a superset of self healing goals.

However, there are scenarios, where we may want self.healing.goals not to be a superset of anomaly.detection.goals. We should drop this enforcement to make such configurations possible.

@efeg efeg added the correctness A condition affecting the proper functionality. label Mar 25, 2021
@efeg efeg self-assigned this Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
correctness A condition affecting the proper functionality.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant