Repository navigation
Six additions for an application that runs beside Kiban. Any active member reads the company's
position and group directories as well as the member one; a position changes hands in one call;
a member can be a guest, present for decisions but shown nobody else; app fragments may say
"and"; decisions read the user's enabled flag straight from Keycloak's database; and merging
the release PR now tags and ships the release.
-
Member-level directories of positions and groups:
GET /api/org/companies/{id}/positionsand.../groupslist id, code and title or name for any active member and an app's service account that is a member, in all three SDKs; the integrate page says to share with a person by granting tomember:<id>#mapped_user -
Decisions read the user's enabled flag from Keycloak's database with one local
SELECT(read-only rolekiban_kcread,KEYCLOAK_DB_NAME), instead of calling the admin REST API on every check; without that database the API answer is cached forKIBAN_USER_STATE_CACHE_SECONDS -
App fragments may use
intersection("and"): a relation that holds only when every child holds, evaluated identically to OpenFGA in the differential harness -
POST /api/org/admin/positions/{id}/handoverends the current assignment and assigns the new member in one transaction, idempotent when the member already holds it, withexpectedAssignmentIdagainst a concurrent administrator; 0.1.x needed two calls and left the position empty in between -
Merging the release PR tags the release: a push to main that changes
VERSIONcreatesv<VERSION>and starts the release workflow; 0.1.x needed a hand-pushed tag -
Guest members:
isGueston a member, set at creation or by a company administrator; a guest is an active member for every decision but is refused the member, position and group directories and a group's member list, so an external person shared with sees nobody else -
Full changelog: https://github.com/rosschiu/kiban/blob/v0.2.0/CHANGELOG.md
-
Known limitations: https://rosschiu.github.io/kiban/latest/limitations/