vocdoni / saas-backend / 28107569777

63%

push

github

feat(api)!: resolve integrator org from the auth context, drop {address} from integrator endpoints

The integrator-scoped endpoints were addressed as /organizations/{address}/...,
but an API key already identifies its integrator org and there is no key-accessible
"whoami" — so a key client couldn't discover the address to build the URL. The
organization is now taken from the authenticated principal, and the endpoints are
path-less.

BREAKING CHANGE: the integrator endpoints move and no longer take an address:
  GET  /organizations/{address}/integrator  -> GET  /integrator
  GET  /organizations/{address}/managed      -> GET  /integrator/managed
  POST /organizations/{address}/managed      -> POST /integrator/managed

- New apicommon.APIKeyFromContext mirrors UserFromContext.
- New a.integratorAddress(w, r): API key -> key.OrgAddress; user session -> the
  integrator org the user administers (selected via subscriptions.IsIntegrator, since
  the user may also administer the managed orgs it created). One user = one integrator
  org in practice (the UI does not let an integrator create more).
- Allowlist + swagger updated; handlers keep their role/quota checks on the resolved org.

Member management is unchanged: POST /organizations/{managedAddr}/members already works
with a key (the managed org's owner defaults to the key owner), and the managed address
comes from the create response.

24 of 27 new or added lines in 2 files covered. (88.89%)

9578 of 15503 relevant lines covered (61.78%)

88.78 hits per line