Deployment without service tables
On this page
Supported APEX installations require no APEXREST service tables or setup DDL. Deployment history and coordination are local.
Implemented
- Plan and apply always use local durable coordination. No APEXREST control table is queried or created; there is no database-backed coordination mode. A legacy
deploymentControl: "local"in old project files is accepted and ignored; other values are rejected. - Local migration history records checksums and
startedbefore SQL execution. Successful migrations are not replayed; changed checksums and unresolved history stop a subsequent plan. - Local ownership serializes apps sharing a DB/service/parsing schema within one managed home. A dead preparing owner may recover; writing ownership after an unknown outcome requires reconciliation.
- Plans bind the coordination scope and local store identity. Source/target drift, authorization, backups, readback verification and restore policy are retained.
- The setup and safety skills state that APEXREST service tables are not prerequisites, so the agent proceeds with
apexrest_shipwithout requesting them for ordinary deployment.
Local state belongs to $APEXREST_HOME/deployment-control/ and must persist between runs. Different machines/homes do not share a lock or migration history: the plugin does not provide cross-machine coordination. Use one durable deployment runner/home and serialize independent machines externally (for example a single CI deploy job).
Verification scope
Local tests cover plan/apply with no control-table calls, persisted migration history, checksum rejection, interrupted-write retention, schema contention, a separate Node runner, dead-owner behavior and store-change rejection. Oracle writes in these tests are explicitly fixtures, not connected deployment evidence. See testing and implementation status for local check scope and remaining release gates.
Connected imports, restore, migration failure injection, authenticated host-browser interactions and independent-machine concurrency require their own integration evidence. Required reports must match the current immutable source before release readiness can pass.