When a parent CI is retired, its associated child CIs are expected to follow the same lifecycle state. However, a key concern is that these CIs (both parent and child) may have dependencies with other servers, applications, or services within the environment.
Directly retiring such CIs without validating their relationships can lead to unintended service disruptions. Therefore, it is necessary to implement a dependency-aware retirement mechanism that:
- Identifies all relationships of the CI
- Verifies whether the CI is still in use by other active services
- Ensures only unused or isolated CIs are retired
