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
When we run mapt to include the target as a ci/cd runner (self hosted runner on gh for the moment, persistent worker for cirrus in the future) do we really need the ssh information? as typically actions executed on the target are driven by the ci/cd system client?
yeah my thinking is also same that its only useful for debugging purposes, but then we need some kind of a way to inject the SSH key later on if we don't want to setup it when initially adding the node as a runner
there might be some way with pulumi to later on run and add the SSH key and we can make mapt capable of doing that, another way without the help of mapt would be to use a github actions job or cirrus ci job to add the SSH key to the node
When we run mapt to include the target as a ci/cd runner (self hosted runner on gh for the moment, persistent worker for cirrus in the future) do we really need the ssh information? as typically actions executed on the target are driven by the ci/cd system client?
Still maybe relevant to debug purposes?
WDYT @anjannath ??
The text was updated successfully, but these errors were encountered: