planRecoveryRetention
Purpose and behavior
Section titled “Purpose and behavior”Inventory the repository’s .outpost, or a transport’s objects, and mark each entry eligible or kept with a reason code under the policy. Removes nothing; an incomplete inventory makes every entry ineligible and quota unknown. An invalid policy, or clean-workspaces or maxWorkspaces with a transporter, rejects with code configuration.
Complete example and detailed rules.
Parameters and properties
Section titled “Parameters and properties”optionsRequiredRecoveryRetentionOptionsRepository or transporter to inspect, retention policy and scan limit.options.transporterOptionalTransport | undefinedPlan over this transport’s objects instead of the repository’s .outpost. Only closed-logs and task-cache apply; clean-workspaces or maxWorkspaces reject with code configuration.options.repositoryOptionalstring | undefinedGit checkout whose .outpost is inspected, default process.cwd(), resolved to its top-level directory; a missing directory rejects with code workspace. With transporter, only recorded in the plan.options.policyRequiredRecoveryRetentionPolicyScopes, minimum age and limits deciding which entries are eligible. Validated before inspection; an invalid or unknown field rejects with code configuration.options.maxEntriesOptionalnumber | undefinedMaximum files and directories scanned under .outpost, or objects listed from transporter, default 100000. Exceeding it marks the plan incomplete, so no entry is eligible.observationOptionalObservationHub | undefinedHub receiving the started, then finished or failed, operation event retention.plan with its duration.