> I suppose it could be made to check if the parent dir did not have > permissions and in such case open the file, clear the contents, and write > data back into it, but this seems a little gross to me. >
I think that would be "gross" if it weren't explicit. What about an explicit nonatomic=yes or overwrite=yes option that enables this? The default would be no (the current behaviour), and the docs could say something like, "by default, Ansible does an atomic move and requires write permission on the file's directory to allow it to create a temporary file; if this option is turned on, the copy is non-atomic and write permission on the directory in not required". > In particular, copy operations on large files would require loading > everything into memory, wouldn't they? > I haven't dived very deep on how atomic_move is implemented, but why would doing this change the memory requirements? Really this is the first time I've ever heard of this being a problem - not > saying I'm not sympahethic - but it's interesting it has not been a request > yet. > Two requests in two months on this mailing list. ;-) Don't worry, we'll be working around this by slightly looser permissions in the meantime. -Ben -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/2ef33cca-3ec3-4604-8a38-47a2f9f89c99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
