In the "Testing Without Mocking" section of the docs it indicates to re-associate input and output plugins with in-memory plugins in order to test the interface. Is there a particular way to do this or is it mostly achieved by having different configuration files for the catalog depending on the environment? And if that's the case I'm guessing it's not possible to use the "add-task" function any longer since it would be necessary to execute different code according to the environment

I’ve just finished a first draft at an environment variable that will disable the kill button on the onyx-dashboard here: https://github.com/onyx-platform/onyx-dashboard/pull/87

@dbernal I’m not sure if this is the best way to do it, but what I’ve settled on for now is a function that takes my catalog data structure and removes the input and output plugins so that in my test environment I can just use the add-task API to replace those with core.async plugins.