It seems pretty typical to create an endpoint if it 404s when setting up a watch. We should just move this into the watch API or perhaps closer to the end application layer in one of the oada-cache UI wrapper libs (e.g., cerebral-module or oada-cache-overmind). Perhaps the watch could be given an ensure:true flag or something similar.
It seems pretty typical to create an endpoint if it 404s when setting up a watch. We should just move this into the watch API or perhaps closer to the end application layer in one of the oada-cache UI wrapper libs (e.g., cerebral-module or oada-cache-overmind). Perhaps the watch could be given an
ensure:trueflag or something similar.