We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened: After tsh logout, db profile can still be found in ~/.pg_service.conf
tsh logout
~/.pg_service.conf
What you expected to happen: All dbs should be cleaned up from db profile files.
As minimally and precisely as possible, describe step-by-step how to reproduce the problem. 0. using self hosted postgres in these steps
tsh login --proxy <proxy>
tsh db login <database>
Scenario 2
tsh db login --cluster <leaf> <leaf-database>
teleport version
Teleport v7.3.5
/etc/os-release
tsh version
Teleport v8.0.0-alpha.1 git: go1.17.2
Please include or attach debug logs, when appropriate. Obfuscate sensitive information!
teleport/tool/tsh/tsh.go
Line 1133 in e938201
tc.SiteName
The text was updated successfully, but these errors were encountered:
--cluster
tsh db
teleport db/app start
It seems not easy to find all clusters and all their local db certs during logout. Doable but requires a list cluster call to proxy for every profile.
logout
In addition, the current getActiveDatabases function only returns valid certs. meaning we never do dbprofile.Delete on expired certs.
getActiveDatabases
dbprofile.Delete
With these bugs, we probably accumulated a lot dead entries in db profile files.
Instead finding all local db certs, alternatively we can do a "cleanup" from the db profile side, to
Sorry, something went wrong.
No branches or pull requests
Description
What happened:
After
tsh logout
, db profile can still be found in~/.pg_service.conf
What you expected to happen:
All dbs should be cleaned up from db profile files.
Reproduction Steps
As minimally and precisely as possible, describe step-by-step how to reproduce the problem.
0. using self hosted postgres in these steps
tsh login --proxy <proxy>
tsh db login <database>
, database added in~/.pg_service.conf
tsh logout
, then check~/.pg_service.conf
Scenario 2
tsh login --proxy <proxy>
tsh db login --cluster <leaf> <leaf-database>
tsh logout
, then check~/.pg_service.conf
Server Details
teleport version
):Teleport v7.3.5
/etc/os-release
):Client Details
tsh version
):Teleport v8.0.0-alpha.1 git: go1.17.2
Debug Logs
Please include or attach debug logs, when appropriate. Obfuscate sensitive information!
teleport/tool/tsh/tsh.go
Line 1133 in e938201
tc.SiteName
is emptyThe text was updated successfully, but these errors were encountered: