Revisiting the Ready status

[chanwit]

After adding features like Outputs and HealthChecks, the "Ready" status of the object has been changed unknowingly, breaking the dependency in a Kustomization chain.

Integration of TF-controller into the GitOps workflow must be first-class supported. It is important to get this behavior fixed and fixed correctly.

We'll discuss here what would be a good behaviour, including the state machine to make the behavior "right."

[Nalum]

What did these change about it that it is now broken?

[chanwit]

@Nalum here it is #302

[chanwit]

After applying, the controller should not make the Ready status true if Health Checks exist, for example.

[Nalum]

Ah so there needs to be a state machine, as you noted, that tracks all the conditions and makes sure there is no condition that would contradict a Ready true condition, if there is then Ready should be false?

[chanwit]

Maybe unknown until it would be either true or false.

[chanwit]

Delivered in v0.13.0