Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(cloud-native): add attribute for SQL database schema in Helm chart #94

Open
iromli opened this issue Jan 27, 2025 · 0 comments · May be fixed by #97
Open

feat(cloud-native): add attribute for SQL database schema in Helm chart #94

iromli opened this issue Jan 27, 2025 · 0 comments · May be fixed by #97
Assignees

Comments

@iromli
Copy link
Contributor

iromli commented Jan 27, 2025

Current Helm chart's values.yaml doesn't have attribute to store SQL database schema.
In postgres-based setup, users may want to use custom schema and avoid public schema.

config:
  configmap:
    # -- SQL database dialect. `mysql` or `pgsql`
    cnSqlDbDialect: mysql
    # -- SQL database host uri.
    cnSqlDbHost: my-release-mysql.default.svc.cluster.local
    # -- SQL database port.
    cnSqlDbPort: 3306
    # -- SQL database name.
    cnSqlDbName: gluu
    # -- SQL database username.
    cnSqlDbUser: gluu
    # -- SQL database timezone.
    cnSqlDbTimezone: UTC
    # -- SQL password file holding password from config.configmap.cnSqldbUserPassword .
    cnSqlPasswordFile: /etc/gluu/conf/sql_password
    # -- SQL password  injected as config.configmap.cnSqlPasswordFile .
    cnSqldbUserPassword: Test1234#

Current workaround is to add GLUU_SQL_DB_SCHEMA to global.userEnvs.normal.

Note that the underlying pygluu.containerlib library sets GLUU_SQL_DB_SCHEMA="" as default.

@iromli iromli changed the title docs(cloud-native): add attribute for SQL database schema feat(cloud-native): add attribute for SQL database schema in Helm chart Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants