Repository navigation
Add manual Seed Admin workflow - #6
Merged
Merged
Conversation
…AWS creds Deploy never creates an Admin account automatically (by design — see docs/decisions.md), and until now the only way to seed one required a local AWS CLI setup plus manually looking up UserPoolId/UsersTableName. Adds .github/workflows/seed-admin.yml: a workflow_dispatch job that reuses Deploy's AWS credentials, resolves both identifiers from the Api/Database stacks' CloudFormation outputs, and runs scripts/seed-admin.ts. Also adds a UsersTableName CfnOutput to DatabaseStack so the table name comes from the stack instead of a hardcoded naming convention duplicated in the workflow. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Hi @ezekielelvis! 👋
Your private repo does not have access to Sourcery.
Please upgrade to continue using Sourcery ✨
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.
Summary
Deploynever creates one automatically, by design (seedocs/decisions.md)..github/workflows/seed-admin.yml: manualworkflow_dispatchjob (email/name/password inputs) that reusesDeploy's AWS credentials, resolvesUserPoolId(Api stack) andUsersTableName(Database stack) from CloudFormation outputs, and runsscripts/seed-admin.ts. No local AWS CLI setup needed.UsersTableNameCfnOutputtoDatabaseStackso the table name is read from the stack rather than a hardcoded naming convention.Test plan
pnpm run typecheck(infrastructure) — cleanpnpm run synth— all stacks synthesize,UsersTableNameoutput presentSeed Adminfrom the Actions tab after this merges and confirm the Admin can log in viaPOST /auth/login🤖 Generated with Claude Code