Deploy it, and see a file move

MFT 2 · 3:31

Once its two secrets are set, the transfer is deployed and run on request, and the first file moves into the archive bucket. The schedule field, a cron expression, repeats the run.

Download the mp4Recorded on 2026.2

What it covers

Setting the FTP password and the bucket key as hidden secrets
Deploying the transfer to devtest the same way as any integration
Running it at once through the direct:mft-run endpoint or the Run now button
The copied file in weikio logs and in the admin UI's row per file
How placement picks the agent that runs the transfer
The schedule field, a cron expression set to every fifteen minutes

Commands in this video

Terminal

$ weikio secret set finance/supplier-ftp-password --env devtest
$ weikio secret set finance/invoice-archive-key --env devtest
$ weikio deploy finance/supplier-invoices --env devtest
$ weikio invoke finance/supplier-invoices --endpoint direct:mft-run
$ weikio logs finance/supplier-invoices --env devtest

Transcript

0:02Last time's transfer is published, but its two secrets are still placeholders.
0:07This video sets them, deploys, and runs it once.
0:14The transfer sits on the hub as version 0.1.0, with its two remote variables.
0:20Its two secrets are placeholders, so nothing runs yet.
0:28Two secrets to set, and the first one is the FTP password.
0:34The bucket key goes in the same way, and each value is typed hidden.
0:41Deploying it is the same command any integration uses:
0:44deploy, the transfer's name, and the environment.
0:49It ends when the agent reports it running.
0:54No waiting for the next scheduled run: one command runs the transfer right now.
1:00The endpoint is direct:mft-run, the run-now entry every transfer carries.
1:14The proof that a file moved is in the logs,
1:17and the command is the one every integration uses.
1:21Every line rclone writes is logged as it is written, file name and size among them.
1:26And there it is in the archive bucket: one file copied.
1:30The admin UI keeps a row for every file a transfer moves:
1:34the time, the file, the action, the size.
1:38Here the action reads Copied, the product's own word for a file that arrived new.
1:44The last lines are rclone's tally of the run: what moved and how long it took.
1:49The logs and the row show the same file.
1:53The two values were typed hidden, and the hub stores them encrypted.
1:58No list ever prints a secret's value,
2:01and each one belongs to the environment it was set for.
2:05The version you published, 0.1.0, is what runs,
2:09a JVM on agent dev exactly as for any integration.
2:14The reply answered at once:
2:16a run is queued and starts when any run in progress has ended.
2:20The admin UI offers the same thing as a button, Run now, on the transfer's page.
2:26Which agent it lands on is decided by placement,
2:30the rule that matches a deployment to the agents that serve it.
2:33The two ends stay variables; only the secrets were missing.
2:39So far a run happened only because we asked for one. The schedule is the part that asks on its own.
2:46The transfer's schedule field is a cron, a time pattern.
2:50The scaffold set it to every fifteen minutes, and we left it as it was.
2:55So the next run comes on its own, without anyone asking for it.
2:59The wait is a matter of minutes, so nobody has to sit and watch.
3:04The next video shapes what moves, with filters.
3:08The transfer is deployed and running, and the JVM is on the agent.
3:13One file has moved from the supplier's server to the archive,
3:16and both sides show it.
3:18The schedule takes it from here, and the next video shapes what moves.

Next in this track

MFT 3 · 3:41 Shape what moves