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.

Sign up for GitHub

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

Jump to bottom

diag_addr parameter not available for teleport db start or teleport app start #8653

Closed
stevenGravy opened this issue Oct 19, 2021 · 0 comments · Fixed by #9220
Closed

diag_addr parameter not available for teleport db start or teleport app start #8653

stevenGravy opened this issue Oct 19, 2021 · 0 comments · Fixed by #9220
Assignees
@greedy52
Labels
application-access bug cli Tickets related to CLI experience database-access Database access related issues and PRs good-starter-issue Good starter issue to start contributing to Teleport
Milestone
8.1

Comments

@stevenGravy
Copy link
Contributor

stevenGravy commented Oct 19, 2021 •
edited
Loading

Description

Unlike teleport start you cannot add the diagnosis address to teleport db start or teleport app start

What happened:

Tried to use --diag_addr as a parameter for teleport db start

What you expected to happen:

--diag_addr is available as a parameter

Reproduction Steps

As minimally and precisely as possible, describe step-by-step how to reproduce the problem.

  1. Attempt to use diag_addr with teleport db start
teleport db start --diag_addr=127.0.0.1:3000
ERROR: unknown long flag '--diag_addr'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@greedy52 greedy52

Labels
application-access bug cli Tickets related to CLI experience database-access Database access related issues and PRs good-starter-issue Good starter issue to start contributing to Teleport
Projects
None yet
Milestone
8.1
3 participants
@r0mant @greedy52 @stevenGravy