[Docs] Clarify that write_files
creates parent folders
#330
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Clarify in documentation that
write_files
will create parent foldersfor paths that do not already exist.
This obfuscates what the problem is when people erroneously create
files in
/tmp
despite the warnings in the documentation not to do so.People naturally assume that their file is absent because the parent folder
did not exist for it to be created in, causing them to add a
runcmd
blockto create the folder, even though execution order means that this will not
occur until after
write_files
have all finished.Might also consider adding an actual warning in log output if a
write_files
block does this.