You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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
👉 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.
CopyToRemote should be able to create parent dirs as needed. it currently errors if the destination dir path doesn't exist
The text was updated successfully, but these errors were encountered: