Rebuild Dispatch with shared services and private DSP state - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace per-DSP application installations with one shared dashboard, API, account service, job runner, auth broker, and provider worker implementation. DSPs now contain private state only. A permanent Dev DSP routes to a separate Preview artifact, and production promotion requires the exact artifact approved on Preview.
The rebuild includes role-based workspace access, invitations and password recovery, DSP lifecycle and audit records, Paycom connections and verification, scheduled collection, employees and timecards, immutable build inventories, controlled activation/rollback tooling, and offline backup/restore. The Plugins page and legacy per-DSP installation framework are removed.
This is a fresh-setup repository. It does not migrate archived platform state automatically. There is no release-publishing or deployment workflow, and building or merging starts no services. Runtime directories and the retained archive are untouched.
Validation:
Native fixture tests retain the outer Linux sandbox and use a local-only exception for Chromium's inner sandbox because of this host's existing AppArmor policy. Production keeps the inner sandbox mandatory. Compatible production-host setup and real Paycom/account acceptance remain deployment prerequisites; no host policy or live provider credentials were changed or used.