Issue-50: Provision Isolated QA Environments for Pull Requests - #51
Draft
klondikemarlen wants to merge 10 commits into
Draft
Issue-50: Provision Isolated QA Environments for Pull Requests#51klondikemarlen wants to merge 10 commits into
klondikemarlen wants to merge 10 commits into
Conversation
Add a local Ruby workflow that builds immutable PR images, provisions disposable Azure sidecars, verifies readiness, and retains retryable cleanup state. See #50.
klondikemarlen
force-pushed
the
issue-50/automated-per-pr-qa-environments
branch
from
July 31, 2026 21:49
6a4a783 to
ff88272
Compare
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.
Fixes #50
Context
Pull request QA currently requires ad hoc deployment of a production-like build and manual cleanup. This adds a disposable, isolated environment workflow that can be operated locally without changing production deployment behavior or the caller's checkout.
Implementation
--allteardown.callpattern.Screenshots
N/A - backend and developer tooling changes only.
Testing Instructions
dev test.dev up.set -eu; ruby -c bin/lib/deploy/temporary/support/service.rb; ruby -c bin/lib/deploy/temporary/command.rb; ruby -c bin/deploy; bin/deploy temporary --help; bin/deploy ephemeral --helpbin/dev test apiandbin/dev test webthrough the documented Docker wrapper.bin/dev check-types.TEMPORARY_DEPLOYMENT_*values, then runbin/deploy temporary up --pr <number>and verify the reported URL, SHA, readiness response, status, logs, and explicit teardown command.bin/deploy temporary down --pr <number>and verify the remote app, blob container, and PR image are removed; usebin/deploy temporary down --all --yesonly when intentionally cleaning every tracked temporary deployment.Observed verification before the focused scope restoration: Ruby syntax checks, deployment formatter and command-help checks, canonical temporary configuration smoke test, API lint, web lint, API type checks, full API tests (23 files/122 tests), web tests (1 file/14 tests), API/web type checks, local production Docker build with temporary arguments, and
git diff --checkpassed. The four unrelated lint-cleanup files were restored as requested. The deployment command smoke check remains a manual QA step because this environment's repository boundary blocks executingbin/deploy. Real Azure/Auth0 provisioning remains operator-dependent because no QA subscription or management token is available in this environment.Learner coverage: no action; this feature is based on a manually requested external-project review, not a repeatable learner miss.