Consolidate web/admin and portal/auth into three application workloads - #1051
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
1 participant
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.
QM currently runs five application workloads even though the surfaces are released together. This change serves admin from web-ui at
/adminand embeds auth in portal, leaving core, web-ui, and portal as three deployed workloads.Logical configuration remains intact; selective deploys and logs resolve to the containing workload. Admin retains signed identities and core authorization. Auth binds to loopback with its existing public route allowlist. Docker, Fly, AWS, Helm, Porter, development tooling, and image smoke checks use the combined layout.
AWS and Fly deploy web before portal. AWS secret uploads defer task activation while hosts still have legacy routing. Conflicting settings and secret destinations fail before deployment. The migration guide covers capacity, secret access, verification, retirement, and rollback. No database change or live infrastructure apply is included.
Validation: affected web/admin/portal/auth/CLI/dev tests, typechecks, ESLint, production-image builds and boot checks, and Helm success/error renders. Independent security and deployment reviews completed with findings resolved. Final focused secret/setup/preflight, migration, and authorization regressions pass. CI is the full-suite gate. The optional Docker lifecycle test could not complete locally because Colima cannot mount the host Docker socket; production-image smoke checks passed separately.
Browser QA reached admin through portal and combined web against a running core. The local instance uses a mock model because no model API key is configured; inference and real email delivery were not exercised.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.