Lifecycle and Status
Lifecycle
Lifecycle is used to inform Governor what is the current state and what Cloud Governor should do with this according this value over a Governed Object.
There are several Lifecycle values
| Lifecycle value | Description |
|---|---|
| Apply | Apply Lifecycle tells Governor he needs to enforce the desired values to the object until it becomes Ready |
| Ignore | Ignore tells Governor to stop and don't try to enforce the desired values |
| Delete | Governor will move the Cloud Object to the Recycle Bin |
| Release | Object is deleted in Governor Database and it will appear in the next List Observation |
| Restore | Governor will Restore the cloud object located in the Recycle Bin |
| Destroy | Governor will permanently delete the object in the cloud |
You can change the Lifecycle value for an Object and then Governor with execute the associated action.
Status
Status indicates if the cloud object is like we want to or not, it can indicate what Governor is doing in this moment with the object.
| Status | Description |
|---|---|
| Ready | Object is as expected |
| Not Ready | Object is not as expected |
| Observing | Object is being (re-)observed |
| Deleting | Object is moving to recycle bin |
| Deleted | Object is in recycle bin |
| Restoring | Object is restoring from recycle bin |
| Restored | Object is restored from recycle bin |
| Destroying | Object is being deleted permanently |
| Destroyed | Object is permanently deleted |
| Decommissioning | Object is finally terminating (end-of-life) |
| Decommissioned | Object reached end-of-life |
| Changing | Object is being changed |
You cannot modify the Status of an object. The Status will be updated by the Governor Engine as part of the reconciling procedure.
Lifecycle Reference
Apply
Apply instructs Governor to establish and keep the desired state for the given object.
If an object is in Apply lifecycle and is manipulated via Portal, the Governor Engine will revert the native object to the desired state as soon as the configuration drift is detected.
| Change Lifecycle to... | Effect |
|---|---|
| Ignore | Ignore any configuration drift on the object. |
| Delete | Move object to recycle bin (if recycle bin support is indicated by the Schema). |
| Destroy | Permanently delete the native object. |
| Release | Drop the object specs from Governor database, but keep the native object intact. |
Ignore
Report configuration drift as "Not Ready" but do not touch the native object.
| Change Lifecycle to... | Effect |
|---|---|
| Apply | Start enforcing the Governor specs to the native object. |
| Delete | Move object to recycle bin (if recycle bin support is indicated by the Schema). |
| Destroy | Permanently delete the native object. |
| Release | Drop the object specs from Governor database. |
- Update the lifecycle on the object to Ignore.
- Add an event.
- Drop pendings orders for this object.
- Compare and reconcile the object.
- Check for pending orders.
- Instruct the reconciler to run the "Ignore"-Check
- All preconditions must be true
- All conditions must be true
- All properties must match the inventory
- If all conditions are matched, the object becomes Ready.
- Otherwise the object becomes Not Ready
Delete
Put the native object into the recycle bin. This lifecycle is only supported for objects where the target system has a recycle bin/restore functionality.
If the target system has no recycle bin, Delete makes no sense at all. The Governor Engine should automatically turn "Delete" into "Destroy" in that case.
| Change Lifecycle to... | Effect |
|---|---|
| Ignore | Ignore any configuration drift on the object. |
| Apply | > will end up in "Restore" |
| Restore | Restore object from native recycle bin (if recycle bin support is indicated by the Schema). |
| Destroy | Permanently delete the native object from the native recycle bin. |
| Release | Drop the object specs from Governor database, but keep the native object in recycle bin. |
Restore
Restore the native object from the recycle bin. This lifecycle is only supported for objects where the target system has a recycle bin/restore functionality.
If the target system has no recycle bin, Restore makes no sense at all. The Governor Engine should automatically turn "Restore" into "Apply" in that case.
| Change Lifecycle to... | Effect |
|---|---|
| Ignore | Ignore any configuration drift on the object. |
| Apply | > will end up in "Restore" |
| any other state | > will end up in a mess (most likely) |
Destroy
Destory instructs Governor to delete the cloud object permanently. No restore is possible, even if the target system provides a recycle bin.)
| Change Lifecycle to... | Effect |
|---|---|
| Apply | Will try to re-create the object. |
| Release | Drop the object specs from Governor database, but keep the native object in recycle bin. |
Release
Drop the Governed Object from the database, but keep the native object intact. By releasing a Governed Object, the engine will drop the desired state, the object will disappear in Governor and Governor will stop reporting configuration drift.
However, as long as the cloud object exists, it will be re-observed on next list observation and re-added to the system.
| Change Lifecycle to... | Effect |
|---|---|
| anything | > is not possible, since the object will be dropped from the database. |
Status Reference
Ready
Ready indicates that the related native object is as declared in Governor. All properties are exactly configured the way the should be.
Not Ready
Not Ready indicates that the related native object is not as declared in Governor. Some configuration values are different, the cloud object is not configured as it is declared in Goveronr.
Observing
Observing indicates that the native object is being observed by the Observer process. As soon as the object is re-observed, Governor will continue to compare the desired state to the actual object and perform further actions if needed.
Deleting
Deleting indicates that the native object is being moved to the native recycle bin. As soon as the object is detected in the recycle bin of the target system, the status will change to "Deleted".
Deleted
Deleted indicated that the native object was found in the recycle bin of the target system and can potentially be restored with a special action.
Governor does currently not track retention times of recycle bin's in the target system.
Restoring
Restoring indicates that the native object is being restored from the native recycle bin.
Restored
Restored indicates that the native object was restored from the native recycle bin.
When the reconciler finds an object in Restored status, it will proceed to "Apply".
Destroying
Destroying indicates that the native object is being permanently deleted from the target system. When the native object is confirmed to be non-existent, the status changes to Destroyed
Destroyed
Destroyed indicates that the native object was successfully dropped from the target system.
Decommissioning
Decommissioning indicates that the Governed Object is being decommissioned.
Decommissioned
Decommissioned indicates that the Governed Object was successfully terminated and any necessary termination action, i.e. export into an archive, has been carried out.
Changing
Indicates that Governor is updating the cloud object to resolve configuration drift.