You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
--simulate-json: consider recording run identity (start time, pid) in the document #32
A run that fails before the JSON write leaves an earlier run's FILE in place. CFEngine's practice, followed here, is to leave the old file, write atomically, and signal failure through the exit status. cf-net get -o, cf-promises -T, cf-secret and cf-runagent all behave that way.
A cheap extra safeguard: put the run's start time and pid in the document, so a consumer can detect an old file without trusting the exit code. cf-monitord's env_data sets the precedent there: its reader checks the file's age. About 5 lines. Not done now to keep the upstream PRs small.
Activity