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
normalize temp dir/file usage (remote_tmp, etc) #31022
Comments
#11937 => Can't use default location of .ansible_async file because it is read-only. |
#28716 pr for 'ansible_async' in remote_tmp |
Another ref: #31617 In cloud-init it seems
Of additional note, python falls back to using the pwd module to determine the homedir, if |
…s a bug about unconditionally using /tmp instead of respecting remote_tmp, and some quirky behavior regarding the ownership of a temporary file used when become_user is a limited user. Also [apt] is added to hosts.ini, and dst has been given the apt role.
Since there are only a couple issues open, we'll handle the rest as individual tickets. |
All subsystems should use same temp dirs (ansiballz, shell+action, modules, async)
Temp dirs should be more configurable (right now they are global, should be host specific)
In doing this we should address/fix the following issues:
#20886#27699 ansiballz not using remote_tmp
#17908(not main issue, but having per host configurable remote_tmp would mitigate)#30064 git module creates script in /tmp which does not work on 'no exec systems'
#30074(not main issue, giving 'url using' module a predictable tmp to write to)#25831read only /tmp#25794#22203#21562#18391(mostly by allowing per host 'world readable tmp files')#13876#16046
#11937#28318#29019#33079#31617Related prs:
#28716ISSUE TYPE
COMPONENT NAME
core
ANSIBLE VERSION
The text was updated successfully, but these errors were encountered: