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
When using the remote-file action w/ a :content key (example below), it generates bash script that assumes the pre-existence of the file you're trying to create.
That last line is the culprit. readlink -f .ssh/config fails because there is no /home/vmfest/.ssh directory. There is a prior (remote-directory ".ssh") call in my code, but that creates the .ssh directory in my admin user's home directory, not in the vmfest user's home directory.
The culprit seems to be in src/pallet/actions/direct/remote_file.clj on line 116 where is calls (create-path-with-template path new-path) with the path (the destination file) as the first argument, template-path. I'm not clear on what the logic should be there, but this seems wrong. It's essentially saying, "the file you're trying to create is the template you should use to create the file."
The text was updated successfully, but these errors were encountered:
When using the remote-file action w/ a :content key (example below), it generates bash script that assumes the pre-existence of the file you're trying to create.
(remote-file ".ssh/config" :content "Host github.com...")
That last line is the culprit.
readlink -f .ssh/config
fails because there is no /home/vmfest/.ssh directory. There is a prior(remote-directory ".ssh")
call in my code, but that creates the .ssh directory in my admin user's home directory, not in the vmfest user's home directory.The culprit seems to be in src/pallet/actions/direct/remote_file.clj on line 116 where is calls
(create-path-with-template path new-path)
with the path (the destination file) as the first argument, template-path. I'm not clear on what the logic should be there, but this seems wrong. It's essentially saying, "the file you're trying to create is the template you should use to create the file."The text was updated successfully, but these errors were encountered: