Follow-up to #236. The tool containers declared restart-on: [runtime-config], so a changed configuration file restarted them. The runtime now does the same for every file resource a module's words name exactly — its configuration and its own secrets — added to the runtime process's restart-on. Directories and unnamed files are not. Test extended; catalogue and command packages pass.
Follow-up to #236. The tool containers declared `restart-on: [runtime-config]`, so a changed configuration file restarted them. The runtime now does the same for every file resource a module's words name exactly — its configuration and its own secrets — added to the runtime process's `restart-on`. Directories and unnamed files are not. Test extended; catalogue and command packages pass.
The tool containers were restarted when their configuration file changed; the runtime now is
too, for every file a module's words name exactly — configuration and own secret alike.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #236. The tool containers declared
restart-on: [runtime-config], so a changed configuration file restarted them. The runtime now does the same for every file resource a module's words name exactly — its configuration and its own secrets — added to the runtime process'srestart-on. Directories and unnamed files are not. Test extended; catalogue and command packages pass.