To production

MFT 5 · 3:59

The invoice transfer from the earlier MFT videos goes to production, where its remotes and secrets have values of their own. A run that fails after the supplier changes its password is found and fixed.

Download the mp4Recorded on 2026.2

What it covers

Remote values for production, with its own server and bucket
Production secrets entered at a hidden prompt with weikio secret set
Promoting the version into production with weikio promote, which pins it there
A production run with weikio invoke, and its Copied rows on the Transferred files page
A failed run after a password change, from Needs attention to the rclone error
Setting the new password and restarting the transfer with weikio restart

Commands in this video

Terminal

$ weikio secret set finance/supplier-ftp-password --env production
$ weikio secret set finance/invoice-archive-key --env production
$ weikio promote finance/supplier-invoices --from devtest --to production
$ weikio invoke finance/supplier-invoices --env production --endpoint direct:mft-run
$ weikio problems
$ weikio logs finance/supplier-invoices --env production --from 2026-10-23T13:04:27Z --to 2026-10-23T13:04:38Z --correlation-id 4cdc9acd-d45b-42bb-918d-421c50553b54
$ weikio restart finance/supplier-invoices --env production

Transcript

0:01The transfer runs in devtest.
0:04This video takes the same three documents to production and reads the runs.
0:13The destination bucket holds the files of two devtest runs.
0:17The next environment is production, with its own agent.
0:21Each environment has its own value for each remote.
0:24Production works against its own server and bucket.
0:31Each environment keeps its own secrets, so production gets its own.
0:36The command prints where the value goes, then asks for it at a hidden prompt.
0:43The bucket key goes in the same way.
0:48Each secret chip takes a production tag when the hub stores the value.
0:56Promote moves the version into production and pins it there.
1:01The command asks before any production write, and the answer is yes.
1:05The production line in the version stack reads 0.1.1 and running.
1:11The promotion touches no remote value and no secret.
1:19The invoke command asks for a run of the transfer in production.
1:25The reply comes at once and says the run is queued.
1:28The run copies the two invoices into the production bucket.
1:34The Transferred files page is filtered to production.
1:38It holds one Copied row for each of the two PDFs, and no other row.
1:45The transfer's page keeps the runs in its Runs section.
1:49Its row counts the run's two files and no errors.
1:57A new invoice reached the supplier's production folder.
2:01The supplier changed its production password off camera.
2:14The newest row shows no files, one error in red, a First error.
2:21Home counts it under Needs attention.
2:28The platform writes a problem when a run fails, and here it reads transfer-failed.
2:34One error shows, and the detail gives a logs command.
2:45Rclone wrote 530, incorrect password.
2:51The new password goes in with the same secret write.
2:56The value stays hidden and never reaches the screen.
3:01The transfer reads its password at startup, so this command restarts it.
3:13The same invoke command asks for a run.
3:16This run uses the new password.
3:21The new invoice arrives in the production bucket.
3:27The problems list has nothing now.
3:33Home shows that nothing needs attention.
3:41Each environment has its own value for each remote.
3:44The promotion pinned the version in production.
3:47Production runs copied all three files.