-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
file state: leading zeros in mode cause unexpected results #661
Comments
slated for 0.9.7 |
Ok, now you can pass a string with a 0, aka: /etc/foobar: |
Did this issue ever get updated to a point where the system could handle the leading zero without quotes? I searched through the issues and didn't see anything (unless I just didn't find the right term). |
This was about a problem in python2, its currently working as expected in python3 and current salt version. |
* test_system: prevent errors when systemd-timesyncd service is masked * test_custom_module: disable tests when running on Salt Bundle * Fix debian 12 package tests * pam: use sys.executable in case /usr/bin/python3 does not exist * pam: add unit test to ensure sys.executable is used * Use proper method to calculate the path to Python interpreter --------- Co-authored-by: Megan Wilhite <mwilhite@vmware.com>
when the data is loaded by yaml.safe_load, a leading zero (which is valid and not uncommon in file modes) will cause the number to be read in as octal, causing "- mode: 0644" to result in a file with mode 420.
If possible, we should find a way to make make "- mode: 0644" work the way it looks like it should.
The text was updated successfully, but these errors were encountered: