Join GitHub today
Reject standalone checks in API before serving "/checks" routes #1417
Motivation and Context
Standalone checks will be picked up by Sensu API if a Sensu Client exists on the same node and they both load checks from the same configuration file and/or directories. Including standalone checks that only exist on the node running Sensu API may be misleading to users as they may expect the API to also show information on standalone checks that exist outside of the API server.
How Has This Been Tested?
Wrote test specs. Ensured they failed prior to the fix and that they passed after the fix.
Screenshots (if appropriate):
Types of changes