refactor(api): replace legacy organization fields with instance scope model #23
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
CT-Automation docs have been updated to remove organization/tenant terminology in favor of CT-Ops instance/client scope language, but the implementation still exposes legacy organization_* names in the API, database schema, domain model, and tests.\n\nEvidence:\n- src/ct_automation/api/app.py still defines pairing and actor payloads with organization_slug, organization_name, and organization_id.\n- src/ct_automation/db/schema.py still has an organizations table and organization_id foreign keys.\n- CT-Ops currently passes its instance id through the old organization_id field in the integration contract.\n\nWhy it matters:\nCT-Ops no longer has organizations, so keeping these names in the runtime API makes the product contract misleading and increases the risk of future CT-Ops integration drift.\n\nSuggested fix:\nIntroduce an explicit instance-scope/client-scope model and migrate request/response fields, actor context, persistence columns, and tests away from organization_* names. Keep a backwards-compatible alias period if existing CT-Ops releases still send organization_id.