search

dbcli / mssql-cli

A command-line client for SQL Server with auto-completion and syntax highlighting
BSD 3-Clause "New" or "Revised" License
1.35k stars 192 forks source link

Option to specify location of configuration directory #454

Closed cjvirtucio87 closed 4 years ago

cjvirtucio87 commented 4 years ago

Hi,

Running mssql-cli causes it to create a config directory. Unfortunately, it appears to do so on the home directory. This is a little troublesome for us, as we run our capabilities on OpenShift, whose guidelines require us to support arbitrary users. Being able to run mssql-cli without being tied to any given user would simplify deployment for us.

Can an option to specify the location of the configuration directory be added?

ellbosch commented 4 years ago

Thanks for the suggestion, however I'm still a bit confused with the exact issue for using a home directory. mssql-cli will create a new config if one isn't found, wouldn't this resolve your issue? Forgive me if I'm not understanding the issue perfectly 🙂

cjvirtucio87 commented 4 years ago

Hi, thanks for the response. OpenShift assigns a dynamically generated user to each container that runs on the cluster at runtime. We can't rely on any particular user, nor can we rely on leveraging the user's home directory. Instead, (per their guidelines) we set group ownership on the executables in an arbitrary folder (usually something like /opt/app) to the root group (gid 0), so that any dynamically generated user can run them (each generated user is part of the root group).

Apologies, turns out I misunderstood what OpenShift was doing. They assign an arbitrary uid to whatever the user is when a container is run; we can still create a specific user with their own home directory. So the .config directory could still be created.

Thank you for your time.