-
-
Notifications
You must be signed in to change notification settings - Fork 746
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
Upon st2ctl reload (or restart), disabled sensors and rules are reenabled. #3016
Comments
There are two different issues here:
We'll track this for one for the first. |
This is a known issue. And will be fixed as part of content management. |
The problem today is that the CLI commands manipulate the models in db but not the YAML files on disk. Writing to files on disk via API is not a great thing. So we are punting the problem until we figure out our content management story which is basically how to load content into the system via files on disk (infra as code) and via APIs and keep them in sync when user switches from one to another. If you want to disable sensors for good today, manipulate the YAML files on disk and then do st2ctl reload —register-all. |
Example to disable a sensor:
Edit:
|
Sensors can be disabled, but not deleted. Upon st2ctl reload (or restart), disabled sensors are reenabled
If you delete the sensor yaml/py from disk, and reload, it still exists (enabled) in the sensor list
The text was updated successfully, but these errors were encountered: