From devtest to production

Delivery 1 · 4:21

The hello integration moves from devtest into production by promotion, and each environment keeps its own values for secrets and variables. A rollback then puts production back on the earlier version.

Download the mp4Recorded on 2026.2

What it covers

A promotion refused because production has no value for the secret
Setting the secret for production with weikio secret set, and the variable with weikio variable set
Promoting with weikio promote into a pinned production deployment
The integration page's panel per environment and its Previous version row
A change published to devtest with weikio run, then promoted
Rolling back with weikio rollback, and the Roll back action in the menu of the production deployment

Commands in this video

Terminal

$ weikio promote sandbox/hello --from devtest --to production
$ weikio secret set sandbox/erp-api-key --env production
$ weikio variable set sandbox/message "hello from production" --env production
$ weikio run ./hello
$ weikio rollback sandbox/hello --env production

Transcript

0:01This video moves the running integration hello from devtest into production,
0:06and back.
0:10The drawing shows your Weik.io installation as the earlier videos left it.
0:15sandbox/hello runs in devtest on agent dev, following latest.
0:20The secret erp-api-key and the variable message have values for devtest only.
0:26An admin set up production and its agent prod, and production has no deployment yet.
0:35The admin UI counts each environment's deployments.
0:42weikio promote sandbox/hello from devtest to
0:48production copies devtest's version into production.
0:51A production write must name the environment, so the Weik.io CLI names both.
0:59The platform checks the write first and refuses it,
1:03because erp-api-key has no value in production.
1:07The refusal prints the command that sets the missing value,
1:11for the environment or the integration only.
1:17A promote copies the version, not the values.
1:21weikio secret set sandbox/erp-api-key for production
1:26gives production the secret's value.
1:29weikio variable set sandbox/message for production writes the value as plain text.
1:35Neither write asks for confirmation, even in production,
1:39because it restarts nothing.
1:41Production now holds both values,
1:43and the tags draw the rule that a value belongs to one environment.
1:51This time the write passes the check,
1:53and the CLI asks for confirmation before writing.
1:57Production gets its deployment at version 0.1.4, running on agent prod.
2:06Production's deployment runs pinned to version 0.1.4,
2:11and a later publish to devtest does not change what production runs.
2:19In the admin UI, hello's page puts the environments side by side.
2:24Devtest runs 0.1.4 and follows latest, production runs 0.1.4.
2:32Production's previous version line is still empty,
2:35because nothing ran in production before this deployment.
2:43The CLI publishes the change, and devtest takes it with weikio run ./hello.
2:49The new version starts there by itself, and production stays on 0.1.4.
2:59The new version is promoted the same way.
3:04Production runs 0.1.6 now, with 0.1.4 under it as its previous version.
3:15weikio rollback sandbox/hello for production rolls the deployment back to its previous version,
3:230.1.4.
3:29On hello's page, devtest runs 0.1.6 and follows latest, production is back on 0.1.4.
3:38The admin UI does the same rollback through
3:41the Roll back action of the deployment menu.
3:48The folder and its change live on your machine.
3:51The hub keeps the versions and each environment's values.
3:55Devtest follows latest and runs the newest version, 0.1.6.
4:01Production stays pinned to 0.1.4.
4:05The secret and the variable hold their own values in production.
4:09The change went through devtest first. The rollback put production back.