Two things have got conflated in this issue.

One is the LIBAPP-level ability to do CRUD-like operations on User objects – Create, Read, Update, Disable. That is complete, so on that basis that can be closed.

The other is the tools-layer ability to do the actual CRUD operations, one of which is HTTP DELETE. This is not complete, as for UX reasons (good or bad) we don't even delete users.

However, I think that's OK. Since this issue was first files, we have other operational UI module code that performs HTTP DELETE – namely in patron-groups, permissions-sets and user permissions. So it's no longer the case that we have no way of exercising the DELETE code in stripes-connect.

Conclusion: this can be closed. I will do so.

@Mike Taylor, we have the ability to mark a user status = inactive which disallows them from logging in. Can we mark this done? Similarly for https://folio-org.atlassian.net/browse/STRIPES-88#icft=STRIPES-88, is that done?

Marked this for the next sprint, because it's a long-running high-level issue that we really need to close. As far as I can see, we'll be able to do that just as soon as we've done the subtask https://folio-org.atlassian.net/browse/STRIPES-88#icft=STRIPES-88 (Disable or Delete in the Users app).

Oooh, subtasks! I've never made those work before, always relied on issue linking. Looks like the way to go, though. We will need another subtask for Create, though.

Or better, I will create sub-tasks for this.