Repository navigation
Add isolated Auth Dev deployment and PR previews - #1103
Merged
Merged
Conversation
Contributor
|
Maple development preview: https://4627cfc7.maple-ca8.pages.dev Commit: Uses development API, billing, flags and PCR configuration. Cloudflare Access applies. |
This branch was successfully deployed
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.
Auth needs its own Dev deployment and previews before production adoption. Add a fixed Dev profile and reuse the existing Auth CI job to test, build and publish relevant changes independently of client releases.
masterpushauth-dev.maple.aimaple-auth-devPages project and update its Auth-specific PR linkauth.maple.aiPath filters cover Auth and its build/publisher inputs. Forks get unprivileged CI without hosted previews. The Dev producer is the existing Auth CI job, avoiding a duplicate build lane. The protected publisher executes trusted master tooling, validates the exact source/run/artifact/target, and treats the uploaded static bundle as untrusted data. Dev publication moves forward even if an unrelated master merge lands during its build; a late older build cannot overwrite a newer published revision. Production keeps its exact-current-master requirement.
The compiled profile fixes backend, public project ID, PCR trust and native identity. Production preserves the existing Research handoff format; the next stacked PR adds Dev native consumers. Research, Agent, SDKs and backend implementation are unchanged here. Auth preview status/comments are separate from Research previews.
Initial Pages/domain/credential setup and the existing
MAPLE_AUTH_PAGES_DEVELOPMENT_ENABLED=trueactivation are still required. Once configured, Dev needs no manual trigger; optional master dispatch remains for recovery. Production uses its independent activation and explicit dispatches, never client release events. This PR does not change live settings or traffic. PR preview URLs do not gain provider/backend callback registrations; real OAuth rehearsal uses stableauth-dev.maple.ai.Validation: 148 Pages tests passed, including automatic Dev, stacked previews, target/provenance rejection, publication ordering and Research compatibility. Workflow lint passed and independent source review found no blockers. The complete local Nix flake check was interrupted by VM disk exhaustion while restoring tools; hosted CI must complete it. The earlier Auth app checks and both profile builds passed; this follow-up changes publication code/workflows and documentation, not Auth runtime code.