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

Connect My Computer #27881

Closed
17 tasks done
ravicious opened this issue Jun 15, 2023 · 1 comment
Closed
17 tasks done

Connect My Computer #27881

ravicious opened this issue Jun 15, 2023 · 1 comment
Assignees
Labels
epic Epic (a collection of other, related issues) teleport-connect Issues related to Teleport Connect.

Comments

@ravicious
Copy link
Member

ravicious commented Jun 15, 2023

RFD 133

Setup

Preview Give feedback
  1. teleport-connect
    gzdunek
  2. teleport-connect
    ravicious
  3. backport/branch/v14 size/md ui
Setup implementation details

Once we agree on the UI, it's likely we'll have to go back to the setup steps and adjust them a little bit. For example, launching the agent during the setup might initially be much simpler than what we'll need later on to get updates on the status of the agent process. However, initially we shouldn't concern ourselves with that, we want to just implement the setup, let's just keep in mind that we're probably have to share some state between the setup doc and the rest of the UI.

The renderer is going to perform all four steps. Some of them will need access to tshd client (such as setting up the roles), while others will need to talk with the main process (such as downloading the agent). Since we need to report the status of each step to the user, it'll be easier to just have some kind of a separate handler for each step.

When checking permissions, always check them for the root cluster - ACL is not defined for leafs.

Joining the cluster

For now just start the agent without checking if the node successfully joined the cluster.

Status UI

Preview Give feedback
  1. teleport-connect
    gzdunek

Agent lifecycle

Preview Give feedback
  1. backport/branch/v14 size/md tsh
  2. size/md ui
  3. backport/branch/v14 size/md ui
  4. backport/branch/v14 size/md ui
  5. backport/branch/v14 size/sm ui

Other

Preview Give feedback
  1. size/lg ui
  2. backport/branch/v14 documentation size/md

Papercuts

Important

Good to have

  • Setup should redirect to Status (as in open the tab) only if Setup is the current active location.
  • Rather minor issue: CreateConnectMyComputerRole should return not certsReloaded, but the name of the created role.
    • The UI should then check if the created role is in the list of roles of the current user. If not, it should sync root cluster details.
    • With the current implementation, in a pristine state if CreateConnectMyComputerRole succeeds but the attepm to GetCluster fails and you attempt to repeat the setup, CreateConnectMyComputerRole will return certsReloaded: false and the app won't attempt to refresh the certs in the UI.
  • Attempt to call RemoveNode after stopping the agent. Otherwise the agent will linger in the cache.
    • This means that the agents need to be stopped before tshd.

Stretch

After release

  • Discover tile with link to docs
@ravicious
Copy link
Member Author

Moved docs & the Discover tile to the new "After release" section. The release of the feature will mean that Connect My Computer is available in Connect. After the release we'll work on getting people to use it.

Removed WSL from the stretch goals. We'll think of WSL if the feature gains traction.

Moved teleport CLI API tests to the stretch goals. The API is unlikely to change, so the tests would not bring as much value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Epic (a collection of other, related issues) teleport-connect Issues related to Teleport Connect.
Projects
None yet
Development

No branches or pull requests

2 participants