Define a clean way to use odbc drivers and odbc.ini
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Description
The Workbench Helm chart provides a value for you to specify an odbc.ini file at config.sessionSecret.odbc.ini that gets mounted to /mnt/session-secret/odbc.ini. However, for users to actually use the connections defined here you also need to:
- Set environment variable
ODBCSYSINI=/mnt/session-secret - Mount the odbcinst.ini file to
/mnt/session-secret/odbcinst.ini - Change the permissions of /mnt/session-secret so everyone can read it
For example, my values.yaml would look like this:
config:
server:
launcher-env: |
ODBCSYSINI=/mnt/session-secret
defaultMode:
sessionSecret: 0444
sessionSecret:
odbc.ini: |
[ProjectAbcDatabase]
Database=project_abc
Driver=PostgreSQL
Password=password
Port=5432
Servername=database-postgresql
UserName=posit_team
odbcinst.ini: |
[PostgreSQL]
Driver = /opt/rstudio-drivers/postgresql/bin/lib/libpostgresqlodbc_sb64.so
RStudioVersion = 2022.11.0
Version = 1.4.54.1001
Installer = RStudio Pro Drivers
Is there a more simple way this could be done? Could there be an option to specifically mount odbc.ini to /etc/odbc.ini which is the default location for this file?
Related issues
- #270
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The example names values.yaml and the config.sessionSecret.odbc.ini, config.server.launcher-env, and config.defaultMode.sessionSecret settings; start by tracing these values through the Workbench Helm chart templates and review related issue #270. Done means the chart provides a simpler supported configuration for the ODBC files, environment variable, and readable permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100