fix: migrate as durable database owner
All checks were successful
Build and Publish Container Image / build-and-push (push) Successful in 37s
All checks were successful
Build and Publish Container Image / build-and-push (push) Successful in 37s
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a028f0-a42f-7582-89a8-ebaad7343834
This commit is contained in:
parent
7a57d9a30f
commit
4143f7c004
5 changed files with 52 additions and 6 deletions
|
|
@ -18,6 +18,11 @@ make migrate
|
|||
make run
|
||||
```
|
||||
|
||||
When migrations use short-lived login roles, set
|
||||
`SBOM_NEXUS_MIGRATION_ROLE` to the reviewed durable owner role. Alembic issues
|
||||
`SET ROLE` before creating or changing any object, so ownership does not become
|
||||
tied to an expiring lease. The production package uses `sbom_nexus_owner`.
|
||||
|
||||
Production deployments should mount a Secret and set
|
||||
`SBOM_NEXUS_DATABASE_URL_FILE` to its `url` file rather than exposing the DSN
|
||||
in a manifest or command argument. The same file setting is consumed by both
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue