Merge pull request #490 from atom4git/main
Docs/authorized_key: clarify that the path key should probably NOT be set SUMMARY Docs: Fixed unclearance in documentation connected wirh relative path Added additional description in documentation. ISSUE TYPE Docs Pull Request COMPONENT NAME authorized_key.py ADDITIONAL INFORMATION Clarify the documentation unclearance in connected with relative path ~/.ssh/authorized_keys The purpose of the pull request is to eliminate ambiguities in the documentation. In our case, when using the ~ sign, we get the user's root directory (although we explicitly specify a different username) Here is the issue and full picture of problem which we want to fix: LINK Closese: #483 Reviewed-by: Gonéri Le Bouder <goneri@lebouder.net> Reviewed-by: atom4git Reviewed-by: Hideki Saito <saito@fgrep.org>
This commit is contained in:
commit
d36a289deb
|
@ -0,0 +1,3 @@
|
|||
---
|
||||
bugfixes:
|
||||
- "Bugfix in the documentation regarding the path option for authorised_key(https://github.com/ansible-collections/ansible.posix/issues/483)."
|
|
@ -28,8 +28,10 @@ options:
|
|||
required: true
|
||||
path:
|
||||
description:
|
||||
- Alternate path to the authorized_keys file.
|
||||
- When unset, this value defaults to I(~/.ssh/authorized_keys).
|
||||
- Alternative path to the authorized_keys file.
|
||||
- The default value is the C(.ssh/authorized_keys) of the home of the user specified in the O(user) parameter.
|
||||
- Most of the time, it's not necessary to set this key.
|
||||
- Use the path to your target authorized_keys if you need to explicitly point on it.
|
||||
type: path
|
||||
manage_dir:
|
||||
description:
|
||||
|
|
Loading…
Reference in New Issue