Files
dokku/tests/unit
Jose Diaz-Gonzalez 0c3ae47299 fix: report config write failures instead of exiting 0
`config:set`, `config:unset` and `config:clear` discarded the result of writing the app's environment, so a write that never landed still printed `Setting config vars`, still fired the `post-config-update` trigger, still restarted the app and still exited 0. The `config-set` and `config-unset` plugin triggers behaved the same way, which meant an `app.json` `env` block that could not be persisted deployed anyway with the variables missing. The environment is now staged in a temporary file and renamed into place, so a write that fails partway leaves the previous environment intact, and that file is created at `0600` rather than being created at `0644` and chmodded afterwards. `apps:clone` and `apps:rename` never applied that chmod at all and left the new app's environment world-readable.
2026-09-18 00:36:38 -04:00
..
2026-05-04 13:16:28 -04:00
2026-05-10 21:42:35 -04:00
2017-02-24 12:41:12 -03:00
2024-03-13 07:47:54 -04:00
2024-03-13 07:47:54 -04:00
2024-01-19 03:51:21 -05:00
2024-02-27 14:19:53 -05:00
2026-05-25 16:07:55 -04:00
2024-02-25 15:54:31 -05:00
2025-11-18 17:06:30 -05:00
2025-11-09 20:21:10 -05:00