This just came up in an Issue 1783. Basically because there was an
exec foo that exited that was causing habitat to restart constantly.
From my understanding, the difference is that
exec causes the child process to “replace” the current process.
I’m not so sure the implications from a Habitat perspective… I know when you don’t use
exec you have to
export your environment variables for the sub process to have access to them.
export FOO_VAR=baz my_process
FOO_VAR=baz exec my_process
What is the recommended best practice? As we can see, having more than one
exec is just wrong, so maybe there should be a linter for that during the build process?