Skip to content

Conversation

@Anamari-ctrl
Copy link

Added instructions for key-based SSH access in Ansible.

Added instructions for key-based SSH access in Ansible.
@ansible-documentation-bot ansible-documentation-bot bot added the new_contributor This PR is the first contribution by a new community member. label Oct 27, 2025
@ansible-documentation-bot
Copy link
Contributor

Thanks for your Ansible docs contribution! We talk about Ansible documentation on Matrix at #docs:ansible.im if you ever want to join us and chat about the docs! We meet on Matrix every Tuesday. See the Ansible calendar for meeting details. We welcome additions to our weekly agenda items too. You can add the dawgs-meeting tag to a forum topic to bring it up at the next meeting.

ansible myhosts -m ping -i inventory.ini
If your managed nodes are configured for key-based SSH access, run:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Anamari-ctrl thanks for the contribution. I'm afraid this reads somewhat off to me though.

All SSH access is key-based. That's the fundamental nature of how SSH works.

I think the --key-file option is available for non-default key locations. For example if you store your private key somewhere other than ~/.ssh you need to tell Ansible where to find it.

In this case I'm not so sure about including this in the getting started guide because it starts adding details that might get in the way. Getting started docs are meant to be light, quick to get through, and relevant for the majority of users. If we start enumerating various parameters for non-defaults and corner cases then I'd be concerned about adding bloat that defeats the purpose of getting started content.

@oraNod oraNod requested a review from samccann December 5, 2025 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new_contributor This PR is the first contribution by a new community member.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants