CopyToRemote should be able to create parent dirs as needed (like `mkdir -p`)

[kumavis]

CopyToRemote should be able to create parent dirs as needed. it currently errors if the destination dir path doesn't exist

[thomas11]

Hi @kumavis, thank you for the suggestion. We decided on not creating the parent dirs mainly because cp and scp don't either, so it's the least surprising behavior. You can always use the Command resource to run mkdir -p before the copy (using dependsOn for sequencing).

[kumavis]

understandable but 👉 in accordance with the philosophy of IaaC 👈 , i want to be able to specify a layout of files on the remote machine and i want pulumi to apply whatever changes are necessary to achieve that state

[kumavis]

an additional note for this, you'd want to be able to specify RWX permissions

[thomas11]

👉 in accordance with the philosophy of IaaC 👈 , i want to be able to specify a layout of files on the remote machine and i want pulumi to apply whatever changes are necessary to achieve that state

That's a fair point! I'll leave this issue open and hope we'll be able to revisit it soon.

[MaleicAcid]

Adding an additional Command to nearly each CopyToRemote resource to create a parent directory is a huge burden for entry-level users with only 200 free resources. Hope CopyToRemote can provide the option to automatically create a parent directory.