Support abra-keycloak plugin via invite command proposal #97

New Issue

decentral1se · 2021-03-12T08:29:15Z

decentral1se commented

2021-03-12 08:29:15 +00:00

abra app id.foo.bar invite foo@bar.com

Would be fantastic.

> abra app id.foo.bar invite foo@bar.com Would be fantastic.

decentral1se added this to the Beta release milestone 2021-03-12 08:29:15 +00:00

decentral1se added the

enhancement

label 2021-03-12 08:29:15 +00:00

decentral1se commented

2021-03-12 08:33:35 +00:00

kawaiipunk ooh Keycloak user management baked into abra, that's a galaxy-brain of an idea 🤔

kawaiipunk oh I just noticed your proposed syntax, that's fire. we could super-easily add it without bloat by making it a per-app command for keycloak, like we've got wp for wordpress or occ for nextcloud. and it could / would have that exact format just whack the relevant stuff in coop-cloud/keycloak/abra.sh

decentral1se is also working on a plugin system for abra in case we wanted to add it higher-level

> kawaiipunk ooh Keycloak user management baked into abra, that's a galaxy-brain of an idea 🤔 > kawaiipunk oh I just noticed your proposed syntax, that's fire. we could super-easily add it without bloat by making it a per-app command for keycloak, like we've got `wp` for `wordpress` or `occ` for nextcloud. and it could / would have that exact format just whack the relevant stuff in `coop-cloud/keycloak/abra.sh` > decentral1se is also working on a plugin system for abra in case we wanted to add it higher-level

3wordchant commented

2021-03-12 09:47:19 +00:00

To demystify my wacky Matrix message, we can stick whatever we want in a sub_invite function in coop-cloud/keycloak/abra.sh and it'd become available as abra app id.foo.bar invite ....

That could use the API via cURL (if we can find a neat way of getting the API key outta the running container), or dive into the container and run CLI commands to create/invite the user.

So, we don't necessarily need to use the abra-level plugin interface -- and we may even prefer not to (what happens when we're running > 1 Keycloak, otherwise?)

To demystify my wacky Matrix message, we can stick whatever we want in a `sub_invite` function in `coop-cloud/keycloak/abra.sh` and it'd become available as `abra app id.foo.bar invite ...`. That could use the API via `cURL` (if we can find a neat way of getting the API key outta the running container), or dive into the container and run CLI commands to create/invite the user. So, we don't necessarily need to use the abra-level plugin interface -- and we may even prefer not to (what happens when we're running > 1 Keycloak, otherwise?)

3wordchant referenced this issue from coop-cloud/keycloak

2021-03-12 09:48:33 +00:00

Add "invite" subcommand to create new users #6

decentral1se added the

plugin

label 2021-04-17 22:45:28 +00:00

decentral1se removed the

plugin

label 2021-06-10 22:40:35 +00:00

decentral1se commented

2021-07-04 20:34:29 +00:00

We've been doing a lot of sub_... work in the abra.sh and it seems like the way to go!