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
A new user of the tool must run their Terraform solution via a Github-managed Ubuntu runner instance. This is a different deployment pattern than how existing users have used the tool thus far (i.e. local clone and local execution).
Since the code is being executed on a remote Github-managed server, there does not appear to be the option to modify the ~/.ssh/config in the runners home directory.
To Do:
Verify if it is truly impossible to modify the runner's ~/.ssh/config file.
Consider an alternate null_resource entry which has the full SSH/SCP CLI commands rather than relying on the ssh_configalias (e.g.tower-dev`).
The text was updated successfully, but these errors were encountered:
A new user of the tool must run their Terraform solution via a Github-managed Ubuntu runner instance. This is a different deployment pattern than how existing users have used the tool thus far (i.e. local clone and local execution).
Since the code is being executed on a remote Github-managed server, there does not appear to be the option to modify the
~/.ssh/config
in the runners home directory.To Do:
~/.ssh/config
file.null_resource entry which has the full SSH/SCP CLI commands rather than relying on the
ssh_configalias (e.g.
tower-dev`).The text was updated successfully, but these errors were encountered: