feat(automations): an upload step — a file from this computer to the … - #14
Merged
Merged
Conversation
…host
A new built-in node, picked from the "+" menu like a snippet ("Upload a file to
the host…"): From this computer, To on the host (a folder ending in / keeps the
name). It goes over the automation's own SSH connection as SFTP, so saved
passwords, 1Password, jump hosts and known host keys all apply. Both paths take
{{params.…}} and {{nodes.…}}, and the node's output is where the file landed:
`docker load < {{nodes.upload.output}}`.
Stored as a node with upload = { from, to } and snippetId "", always targeting
the host; export bundles skip it when gathering snippets.
Local nodes now run in the home folder instead of the app's working directory
(the install folder, often not writable), and an upload's relative path means
the same folder, so `docker save -o image.tar` followed by an upload of
image.tar.gz just works.
Also fixes the editor's "needs a host parameter" check, which read a field that
no longer exists and never fired.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…host
A new built-in node, picked from the "+" menu like a snippet ("Upload a file to the host…"): From this computer, To on the host (a folder ending in / keeps the name). It goes over the automation's own SSH connection as SFTP, so saved passwords, 1Password, jump hosts and known host keys all apply. Both paths take {{params.…}} and {{nodes.…}}, and the node's output is where the file landed:
docker load < {{nodes.upload.output}}.Stored as a node with upload = { from, to } and snippetId "", always targeting the host; export bundles skip it when gathering snippets.
Local nodes now run in the home folder instead of the app's working directory (the install folder, often not writable), and an upload's relative path means the same folder, so
docker save -o image.tarfollowed by an upload of image.tar.gz just works.Also fixes the editor's "needs a host parameter" check, which read a field that no longer exists and never fired.
What and why
How it was tested
Checklist
npm run checkandnpm testpass