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

Updated Session URL #906

Merged
merged 1 commit into from
Apr 7, 2017
Merged

Updated Session URL #906

merged 1 commit into from
Apr 7, 2017

Conversation

russjones
Copy link
Contributor

@russjones russjones commented Apr 7, 2017

Purpose

As reported in #900, the output of teleport status is currently incorrect. The path to a session has changed and the output of teleport status has not beed updated.

Implementation

  • In lib/srv/exec.go we now export SSH_TELEPORT_HOST_UUID and SSH_TELEPORT_CLUSTER_NAME as these are ended to construct the path to a session now.
  • In tool/teleport/common/teleport.go we now list the Host UUID and Cluster Name in addition to the corrected Session URL.

Related Issues

Fixes #900

@@ -182,13 +182,23 @@ func onStart(config *service.Config) error {
func onStatus() error {
sid := os.Getenv("SSH_SESSION_ID")
proxyHost := os.Getenv("SSH_SESSION_WEBPROXY_ADDR")
tuser := os.Getenv("SSH_TELEPORT_USER")
teleportUser := os.Getenv("SSH_TELEPORT_USER")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

constant used more than once, makes sense to make it real constant, otherwise LGTM

@russjones russjones merged commit 1cc89e8 into master Apr 7, 2017
@russjones russjones deleted the rjones/teleport-status branch April 7, 2017 17:23
hatched pushed a commit to hatched/teleport-merge that referenced this pull request Nov 30, 2022
hatched pushed a commit that referenced this pull request Dec 20, 2022
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 this pull request may close these issues.

2 participants