ansible / mazer

Experimental Ansible Galaxy Content Manager
GNU General Public License v3.0
114 stars 18 forks source link

Add default/config/cli option for a tmp or spool dir (dir to download artifacts to) #282

Open alikins opened 5 years ago

alikins commented 5 years ago

Feature Request

Use Case

Right now, mazer installs always download artifacts to temporary paths in /tmp. Aside from being messy, it is also writing to a widely writable dir (/tmp).

Mazer could download artifacts to a known dir owned by the uid (~/.ansible/mazer_tmp or ~/.ansible/tmp for ex), and avoid any potential /tmp problems.

If mazer user a user or group owned dir for storing downloaded artifacts, it could also cache or spool them. It would also avoid the need for 'mkstemp' style tmp file names, which would make it easier to figure out what is what.

If the mazer tmp dir is on same fs as the collections_path, then mazer install could use more atomic file installation mechanisms (ie, extract to a dir somewhere in mazer_tmp, then 'mv' the dir into the final path in one step)

Proposed Solution

Describe the solution you'd like A clear and concise description of what you want to happen. Add any considered drawbacks.