Lifecycle management rules in GCP - Step-by-Step Execution

Process Flow - Lifecycle management rules

Define lifecycle rule

↓

Rule conditions checked

↓

If conditions met?

No→Wait for next check

Yes↓

Perform action (e.g., delete, archive)

↓

Update object state

↓

Repeat for all objects

Lifecycle management rules check objects regularly and perform actions like deleting or archiving when conditions are met.

Execution Sample

GCP

lifecycle_rule = {
  "condition": {"age": 30},
  "action": {"type": "Delete"}
}

object_age = 35

if object_age >= lifecycle_rule["condition"]["age"]:
  perform_action = lifecycle_rule["action"]["type"]

This code checks if an object is older than 30 days and deletes it if true.

Process Table

Step	Object Age	Condition (age >= 30)	Action Taken	Result
1	35	True	Delete	Object deleted
2	25	False	None	Object kept
3	30	True	Delete	Object deleted
4	29	False	None	Object kept
Exit	-	No more objects to check	-	Lifecycle process ends

💡 All objects checked, lifecycle rules applied where conditions met

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
object_age	varies	35	25	30	29	-
condition_met	False	True	False	True	False	-
action	None	Delete	None	Delete	None	-

Key Moments - 2 Insights

Why does the action only happen when the object age is equal or greater than 30?

Because the lifecycle rule condition checks if the object age is at least 30 days (see execution_table steps 1 and 3 where condition is True and action is Delete).

What happens if the object age is less than 30?

No action is taken and the object is kept (see execution_table steps 2 and 4 where condition is False and action is None).

Visual Quiz - 3 Questions

Look at the execution table, what is the action taken when object age is 25?

A Delete

B Archive

C None

D Update metadata

💡 Hint

Check execution_table row 2 under 'Object Age' 25 and 'Action Taken'

At which step does the lifecycle rule delete the object?

A Step 1

B Step 2

C Step 4

D Exit

💡 Hint

Look at execution_table rows where 'Action Taken' is Delete

If the condition changed to age >= 40, what would happen at step 1 with object age 35?

A Delete

B None

C Archive

D Error

💡 Hint

Refer to variable_tracker and execution_table condition logic

Concept Snapshot

Lifecycle management rules:
- Define conditions (e.g., age >= 30 days)
- Check objects regularly
- If condition met, perform action (Delete, Archive)
- Helps automate storage management
- Saves cost by removing old data

Full Transcript

Lifecycle management rules in cloud storage work by defining conditions such as object age. The system checks each object regularly. If an object meets the condition, like being older than 30 days, an action such as deletion is performed. Otherwise, the object is kept. This process repeats for all objects to automate storage cleanup and cost savings.