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.

Sign up for GitHub

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

Jump to bottom

adds warning note and fixes small typo #591

Merged
merged 5 commits into from
Aug 23, 2024
Merged

adds warning note and fixes small typo #591

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
2d4dba4
adds warning note and fixes small typo
Aug 22, 2024
ff2050b
removes s
Aug 22, 2024
d661969
Merge branch 'main' of https://github.com/spacelift-io/user-documenta…
Aug 22, 2024
28f918e
fixes typo
Aug 23, 2024
708fd17
removes s
Aug 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/vendors/ansible/reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ If you use `ansible.cfg` file within a repository (or - more generally - within

If you are using SSH to connect to your hosts, then you need to make sure that private keys delivered to the worker have the correct permissions.

As the ssh man page states:
As the ssh main page states:
> These files contain sensitive data and should be readable by the user but not accessible by others (read/write/execute). `ssh` will simply ignore a private key file if it is accessible by others.

Typically, you would like to deliver private keys directly at the [worker level](../../concepts/worker-pools) where you can fully manage your environment. If that is not an option, you can always use our [read-only](../../concepts/configuration/environment.md#a-note-on-visibility) [mounted files](../../concepts/configuration/environment.md#mounted-files) or any other option you find suitable.
3 changes: 3 additions & 0 deletions docs/vendors/terraform/external-modules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,9 @@ chmod 600 ~/.netrc

Using SSH isn't much more complex, but it requires a bit more preparation. Once you have a public-private key pair (whether it's a [personal](https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account){: rel="nofollow"} SSH key or a single-repo [deploy key](https://docs.github.com/en/developers/overview/managing-deploy-keys#deploy-keys){: rel="nofollow"}), you will need to pass it to Spacelift and make sure it's used to access your VCS provider. Once again, we're going to use the [mounted file](../../concepts/configuration/environment.md#mounted-files) functionality to pass the _private_ key called `id_ed25519` to your stack's environment:

!!! warning
Please note: The file must explicitly be called `id_ed25519`, otherwise your runs will fail with a `Permission denied` error.

![](<../../assets/screenshots/Mouse_Highlight_Overlay (5).png>)

Add the following commands as ["before init" hooks](../../concepts/stack/stack-settings.md#before-init-scripts) to "teach" our SSH agent to use this key for GitHub:
Expand Down
Loading