ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-06-01 13:59:09 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Clarify docs re mode's octal representation (#44410)

Browse source 
* Clarify docs re mode's octal representation

I changed the language about how to use mode to make it more obvious
that using "01777" is not a typo, because the leading zero is not meant
to reflect the way that number might have been given on a command line.
See also: issues #5409 #9196 #11385 #13115 #18952 #23491 #23521
This commit is contained in:
Todd Walton 2018-08-29 16:12:32 -04:00 • committed by Alicia Cozine
parent d5ed818e7c
commit 1247f4a464
4 changed files with 10 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

4
lib/ansible/utils/module_docs_fragments/files.py
View file

@ -27,8 +27,8 @@ options:
mode:
description:
- "Mode the file or directory should be. For those used to I(/usr/bin/chmod) remember that modes are actually octal numbers.
You must either specify the leading zero so that Ansible's YAML parser knows it is an octal
number (like C(0644) or C(01777)) or quote it (like C('644') or C('0644') so Ansible
You must either add a leading zero so that Ansible's YAML parser knows it is an octal
number (like C(0644) or C(01777)) or quote it (like C('644') or C('1777')) so Ansible
receives a string and can do its own conversion from string into number. Giving Ansible a number
without following one of these rules will end up with a decimal number which will have unexpected results.
As of version 1.8, the mode may be specified as a symbolic mode (for example, C(u+rwx) or C(u=rw,g=r,o=r))."