docs: get dev secrets from OpenBao, keep env files as the manual setup #94
No reviewers
Labels
No labels
bug
chore
data
feature
frontend
good first issue
intermediate
needs/docs
needs/research
needs/upstream
type/bug
type/external
type/feature
type/refactor
urgency
high
urgency
immediate
urgency
low
urgency
medium
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ScottyLabs/cal!94
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/openbao-setup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The getting-started guide now pulls dev secrets from OpenBao instead of asking the tech lead for env files:
bao login -address=https://secrets.scottylabs.org -method=oidc, thensecretspec run -P dev -- ...for the API, web app and migrations. Governance already gives/projects/calmembers read access tocal/dev.web/.env.development(committed, unignored) holds the two public local values,NEXT_PUBLIC_API_URLandAPP_URL, which are not in the dev profile.next builddoes not read it.Tested from this branch:
secretspec check -P devfinds all 21 values, the API comes up and reads the dev database, and/api/auth/loginredirects to Keycloak with the cal-dev client.