Need a better way to enforce sequence of code update steps about phosphor-bmc-code-mgmt

[bradbishop]

The good part is that the C++ code does not have to call the system units one-by-one

If we have scripts calling other scripts I wonder if that could be simplified or reduced down to a single script?

Are there any other benefits besides the one above to using systemd over a more conventional implementation for launching scripts/programs, such as this one:
https://github.com/openbmc/jsnbd/blob/master/nbd-proxy.c#L379

[leiyu-bytedance]

Is it possible to add some Wants/Before/After configs in the unit files to solve the issue?
The good part is that the C++ code does not have to call the system units one-by-one anymore, instead, it calls one systemd unit, and the unit will start other systemd units by sequence.

[anoo1]

Is it possible to add some Wants/Before/After configs in the unit files to solve the issue?

Partially. The remaining issue is that we want the function to return until the script (run by a service file) is complete. For example a Delete or Set Priority call would not return to the caller until the operations finished.

Are there any other benefits besides the one above to using system over a more conventional implementation for launching scripts/programs

Hadn't thought of that. That could be an option, instead of executing the script via a service file.

[anoo1]

Adding function for running commands in child process:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-bmc-code-mgmt/+/39844

[anoo1]

Closing. First function (factory reset) migrated to exec instead of using systemd service files.