Skip to content

Helm quickstart: db schema init fails, dbscripts dir uses hyphens not underscores #4120

Description

@senthalan

Description

The Helm tab of the "Get started" guide (guides/getting-started/get-thunderid) creates databases named runtime_transient and runtime_persistent (underscores), then applies schemas with:

for db in configdb runtime_transient entitydb runtime_persistent; do
  kubectl exec thunderid-dbinit -- cat /opt/thunderid/dbscripts/$db/postgres.sql | \
    kubectl exec -i postgresql-0 -- env PGPASSWORD=dbpassword psql -U dbuser -d $db
done

This fails for runtime_transient and runtime_persistent because the schema directories shipped in the release image are named runtime-transient and runtime-persistent (hyphens), not with underscores. configdb and entitydb work fine since those names match their directories exactly.

Steps to Reproduce

  1. Follow the Helm tab of the "Get started" guide
  2. Run the "Apply the database schemas" step
  3. The command fails with something like:
    cat: /opt/thunderid/dbscripts/runtime_transient/postgres.sql: No such file or directory
    
    (same for runtime_persistent)

Version

Latest alpha release

Environment Details (with versions)

  • Kubernetes (Helm)
  • PostgreSQL (Bitnami chart, oci://registry-1.docker.io/bitnamicharts/postgresql)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions