Skip to content
Weik.ioUniversity
Try Weik.io

From devtest to production

Delivery 1 · 3:56

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 and the variable for production with --env
  • 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
  1. 0:01hello runs in devtest.
  2. 0:04This video shows the move out, and back.
  3. 0:10On agent dev, the deployment is running at version 0.1.4, in project sandbox.
  4. 0:17Secret erp-api-key and variable message hold values for devtest.
  5. 0:22An admin made the environment production, and agent prod.
  6. 0:30Home shows one cell per environment, and production's cell shows zero deployments.
  7. 0:39Now the promote: the version that runs in devtest goes into production.
  8. 0:44It names the integration, and each environment by name.
  9. 0:51The y is typed at the prompt, and the promote runs.
  10. 0:54The platform refuses: production holds no value for the secret.
  11. 0:59The line under it prints the command that sets that value.
  12. 1:06Every environment holds its own value for a secret or a variable.
  13. 1:11The secret is set for production, --env names it.
  14. 1:15The secret value goes in on standard input, and it never appears.
  15. 1:19The variable takes its value typed in plain: hello from production.
  16. 1:24Now production holds both: the secret and the variable.
  17. 1:29A promotion copies the version, and the values stay with the environment.
  18. 1:37weikio promote asks for confirmation before it writes into production.
  19. 1:43I type y, and the production deployment is created at 0.1.4, pinned.
  20. 1:52A write keeps the version it replaced as the previous version. Here there is none.
  21. 2:01The admin UI shows the same state, on its integration page.
  22. 2:06The page shows one panel per environment. The production panel reads Version 0.1.4,
  23. 2:14and its Previous version row reads a dash.
  24. 2:21The change is one line in the route, and I publish it with weikio run.
  25. 2:26The folder holds three files, and the edit is in one of them.
  26. 2:33The version list has 0.1.6 on top, with latest.
  27. 2:44I promote the new version.
  28. 2:51Production moves to 0.1.6, and its line reads previous 0.1.4.
  29. 3:00Rollback points the deployment back,
  30. 3:03and the version it replaced becomes the new previous version.
  31. 3:10Its production cell now reads 0.1.4, and the devtest cell stays at 0.1.6.
  32. 3:18The page shows the Roll back action in the production deployment menu.
  33. 3:26Your machine holds the folder, and the hub holds the versions.
  34. 3:31Devtest runs 0.1.6 on latest, and production runs 0.1.4, pinned.
  35. 3:39Production keeps its own value for the secret and the variable.
  36. 3:43A change went to devtest first, and rollback put production back.