pub struct LifecycleManager { /* private fields */ }Expand description
Per-bucket lifecycle configuration manager.
All read / write operations go through RwLock for thread safety;
clones are cheap (Arc<LifecycleManager> is the expected handle shape).
actions_total is a parallel RwLock<HashMap<...>> of (bucket, action_label) -> count so the future background scanner can stamp
successful actions and operators can GET /metrics to see the running
totals (the metric is also surfaced via metrics::counter! — see
crate::metrics::record_lifecycle_action).
Implementations§
Source§impl LifecycleManager
impl LifecycleManager
Sourcepub fn put(&self, bucket: &str, config: LifecycleConfig)
pub fn put(&self, bucket: &str, config: LifecycleConfig)
Replace (or create) the lifecycle configuration for bucket. Drops
any previously-attached rules in one shot — matches AWS S3
PutBucketLifecycleConfiguration (full replace, no merge).
Sourcepub fn get(&self, bucket: &str) -> Option<LifecycleConfig>
pub fn get(&self, bucket: &str) -> Option<LifecycleConfig>
Return a clone of the bucket’s configuration, if any.
Sourcepub fn delete(&self, bucket: &str)
pub fn delete(&self, bucket: &str)
Drop the bucket’s lifecycle configuration (idempotent — missing bucket is OK).
Sourcepub fn to_json(&self) -> Result<String, Error>
pub fn to_json(&self) -> Result<String, Error>
JSON snapshot for restart-recoverable state. Pair with
Self::from_json.
Sourcepub fn from_json(s: &str) -> Result<Self, Error>
pub fn from_json(s: &str) -> Result<Self, Error>
Restore from a JSON snapshot produced by Self::to_json. Action
counters are intentionally not snapshotted — they’re transient
observability data and should reset across process restarts so
rate(s4_lifecycle_actions_total[1h]) doesn’t double-count.
Sourcepub fn evaluate(
&self,
bucket: &str,
key: &str,
object_age: Duration,
object_size: u64,
object_tags: &[(String, String)],
) -> Option<LifecycleAction>
pub fn evaluate( &self, bucket: &str, key: &str, object_age: Duration, object_size: u64, object_tags: &[(String, String)], ) -> Option<LifecycleAction>
Evaluate which rule (if any) applies to a single current-version
object right now. Walks the bucket’s rules in declaration order;
returns the first matching action. Returns None when no rule
matches (or when the matching rule is Disabled, or when the
bucket has no lifecycle configuration).
Within a single rule the precedence is:
- Pick the deepest transition whose
daysthreshold is currently met (= largestdays ≤ object age). - Conflict with expiration: if
expiration_days <= transition_daysfor the chosen transition, expiration wins (the rule wants the object gone before it would have been transitioned). Otherwise transition wins (e.g. transition at 30d, expiration at 365d, age 60d → transition fires now, expiration is future). expiration_datematches whennow >= expiration_dateand no transition is currently applicable.
object_age is “now - created_at” supplied by the caller — keeping
the evaluator pure of the wall clock makes deterministic testing
trivial.
Sourcepub fn evaluate_with_flags(
&self,
bucket: &str,
key: &str,
object_age: Duration,
object_size: u64,
object_tags: &[(String, String)],
flags: EvaluateFlags,
) -> Option<LifecycleAction>
pub fn evaluate_with_flags( &self, bucket: &str, key: &str, object_age: Duration, object_size: u64, object_tags: &[(String, String)], flags: EvaluateFlags, ) -> Option<LifecycleAction>
Full-form evaluator with flags for noncurrent-version handling.
Use this when the scanner is walking a versioning-enabled bucket;
pass is_noncurrent = true for entries that are not the latest
non-delete-marker version.
Sourcepub fn record_action(&self, bucket: &str, action: &LifecycleAction)
pub fn record_action(&self, bucket: &str, action: &LifecycleAction)
Stamp the per-bucket action counter and bump the matching Prometheus counter. Called by the future scanner after a successful delete / metadata rewrite.