[mike-gorman-bitwarden]

🎟️ Tracking

Follow-up to ADR-0036 (#865).

📔 Objective

Adds ADR-0045, "API standards for acting upon resources", with status Proposed. Sets how operations outside create, read, update, and delete are exposed, as actions at /{resource plural}/{id}/actions/{action}, and that asynchronous work returns 202 with a job. Defining the job resource is left to a later ADR.

[cloudflare-workers-and-pages]

Deploying contributing-docs with    Cloudflare Pages

Latest commit:	3360db0
Status:	✅  Deploy successful!
Preview URL:	https://02c9c24f.contributing-docs.pages.dev
Branch Preview URL:	https://docs-adr-0045-api-standards.contributing-docs.pages.dev

View logs

[rkac-bw]

From the database side:

1. Actions are POSTs, so they have the same retry problem as creates. A retried send-email or rotate-key runs twice. The idempotency mechanism suggested on ADR-0042 should cover actions as well.
2. For the follow-up job ADR: please include where job records are stored, how long they are retained, and how callers poll (with Retry-After on 202 and on job reads). Jobs will be the home of long-running work such as backfills and bulk changes, so their storage and polling cost matter.

[mike-gorman-bitwarden]

1. Same answer as on ADR-0042: no new header. Many actions are naturally idempotent (disabling a disabled user does nothing). For those that aren't, the body shape is open, so an action can take a caller-chosen ID and ignore a repeat. Whether it needs to is up to each API.
2. How a caller follows a job's progress, including polling and Retry-After, is already planned for the job ADR. Where a service stores its jobs and how long it keeps them is up to that service.

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

This PR adds ADR-0045 (status Proposed), which defines how operations outside create, read, update, and delete are exposed as POST /api/v1/{resource plural}/{id}/actions/{action}, and requires asynchronous work to return 202 Accepted with a job. The frontmatter, AdrTable usage, RFC 2119 notation section, and MADR structure match ADR-0036 and the ADR index template. ADR-0039 and ADR-0046 are mentioned as plain text rather than links, which fits ADRs that are not yet on main. No issues found.

[mike-gorman-bitwarden]

This PR is superseded by #894. We have done our best to retain/incorporate all feedback received to date.