You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The content you are editing has changed. Please copy your edits and refresh the page.
The icon should be visible when the user has permissions to set up Connect My Computer or if the agent has been already set up (Connect my Computer: Various fixes #31794)
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.
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.
RFD 133
Setup
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
Agent lifecycle
Other
Papercuts
Important
GenerateUserCerts
behavior (Get accessInfo based on user on access request drop #31068) or ask for relogin during setup.ravicious/cmc-portal-example
.Good to have
Setup should redirect to Status (as in open the tab) only if Setup is the current active location.CreateConnectMyComputerRole
should return notcertsReloaded
, but the name of the created role.CreateConnectMyComputerRole
succeeds but the attepm toGetCluster
fails and you attempt to repeat the setup,CreateConnectMyComputerRole
will returncertsReloaded: false
and the app won't attempt to refresh the certs in the UI.RemoveNode
after stopping the agent. Otherwise the agent will linger in the cache.Stretch
teleport
CLI API tests (detecting breaking changes)After release
The text was updated successfully, but these errors were encountered: