-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
~
gets evaluated when using community.general.osx_defaults
#5234
Comments
Files identified in the description: If these files are incorrect, please update the |
The problem is that |
Would it break anything to set the flag to |
I think that should be ok. (Every change breaks something: https://xkcd.com/1172/) |
* Add expand_user_and_vars flag to write Closes #5234 * Add changelog * Update changelogs/fragments/5243-osx-defaults-expand-user-flags.yml Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: Felix Fontein <felix@fontein.de>
* Add expand_user_and_vars flag to write Closes #5234 * Add changelog * Update changelogs/fragments/5243-osx-defaults-expand-user-flags.yml Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: Felix Fontein <felix@fontein.de> (cherry picked from commit f929422) Co-authored-by: Pavel Zwerschke <pavelzw@gmail.com>
…ions#5243) * Add expand_user_and_vars flag to write Closes ansible-collections#5234 * Add changelog * Update changelogs/fragments/5243-osx-defaults-expand-user-flags.yml Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: Felix Fontein <felix@fontein.de>
…ions#5243) * Add expand_user_and_vars flag to write Closes ansible-collections#5234 * Add changelog * Update changelogs/fragments/5243-osx-defaults-expand-user-flags.yml Co-authored-by: Felix Fontein <felix@fontein.de> Co-authored-by: Felix Fontein <felix@fontein.de>
Summary
When passing
~
as value to thecommunity.general.osx_defaults
plugin, it gets directly evaluated to/Users/pavelzwerschke
.This is probably because the value is not passed with quotes to the command line.
When doing it manually, we get the same problem:
Instead, we want ansible to do something like this:
Also, when executing the playbook twice, it still says
changed
instead ofok
the second time because the string comparison is still evaluated tofalse
.Issue Type
Bug Report
Component Name
community.general.osx_defaults
Ansible Version
Community.general Version
Configuration
OS / Environment
macOS 12.5.1
Steps to Reproduce
Expected Results
Expected:
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: