Open jeroenmaelbrancke opened 7 years ago
I'd rather not "fix" this, as our code should be in charge of registering nsm clusters with the abm once required. External clusters can be set up separately, and there are API calls to start using an NSM on a given ABM, and the framework will do all required actions.
After some discussions with @wimpers, @jeroenmaelbrancke, @domsj just re-throw the error, but slightly more readable.
In the future, we might want to implement sth where NSMs can be removed again, and we can validate whether an NSM is already in use by some ABM, so we can be a bit smarter here.
Readding a backend (delete, add) with external Arakoons ends up with errors:
You can fix this with checking the list-nsm-hosts on the abm and if not present register else return