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

[ Enhancement ] Investigate options for how to SSH when base ssh_config cannot be modified with Include statement #91

Open
2 tasks
gwright99 opened this issue Jun 21, 2024 · 0 comments
Assignees

Comments

@gwright99
Copy link
Collaborator

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`).
@gwright99 gwright99 self-assigned this Jun 21, 2024
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

No branches or pull requests

1 participant