pub fn serving_replaced_code() -> Option<String>Expand description
Why this process is serving code that is no longer on disk, or None while the file it
was started from is still the file at that path. The same judgement the lease reader
makes from outside (ExecutableIdentity::replaced), made by the process about itself,
so that the endpoint a client asks for readiness can say so.
use majordomus_cli::lease::serving_replaced_code;
assert!(serving_replaced_code().is_none(), "a test binary has not been replaced under it");