Add AWS tooling smoke harness - #1
Draft
dhempler wants to merge 2 commits into
Draft
Conversation
The smoke suite (scripts/smoke-aws-tooling.mjs) and the 40 example
output fixtures it validates against, split out of the installer PR to
keep its review surface focused. Exercises every deploy/installer
script against stubbed aws/gh binaries; run it with invalid AWS
credentials in the environment so its few live-CLI scenarios cannot
touch a real account:
env AWS_ACCESS_KEY_ID=SMOKEINVALID AWS_SECRET_ACCESS_KEY=x \
AWS_SESSION_TOKEN=x AWS_CONFIG_FILE=/dev/null \
AWS_SHARED_CREDENTIALS_FILE=/dev/null yarn smoke:aws-tooling
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The validator now defaults to the data-api runner, which requires a B1Admin typescript package and DatabaseSecretArn in the outputs file; the scenario stubs typescript (mirroring the vite stub) and provides data-api-shaped outputs instead of the removed direct-runner inputs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
dhempler
force-pushed
the
codex/aws-self-hosting-installer-pr
branch
from
August 13, 2026 19:49
3c0741c to
a1d5e01
Compare
dhempler
force-pushed
the
codex/aws-tooling-smoke-harness
branch
from
August 13, 2026 19:49
e453594 to
2103787
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
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.
Summary
scripts/smoke-aws-tooling.mjsplus the 40 example output fixtures it validates againstWhat the suite covers
aws/ghbinaries prepended to PATH: argument validation, output contracts against the example fixtures, failure-path messaging, and the guided installer's full state-machine walkthrough (IAM apply, private-repo sync, the post-adopt redeploy loop)Testing
Passes clean (
AWS tooling smoke checks passed., exit 0). Always run it with invalid AWS credentials as above: a few scenarios invoke the realawsCLI expecting failure, and on a machine with live credentials they would otherwise touch a real account.Merge order
Stacked on the installer branch. Review/merge after the installer PR; if the installer PR is merged into ChurchApps first, this branch can be retargeted or reopened against ChurchApps/B1Admin main.