Open nluaces opened 6 days ago
At present the status is only set to OK when ready and the connector is only ready when configured and matched. So the behaviour observed is what the code is currently 'supposed' to do.
I guess the question is how the status message should be set. One option would be to set a message that indicates any unmet conditions if the resource is not ready. E.g. in this case a status of 'not matched' or similar. Thoughts?
That sounds good to me. I ran into this by trying two cases:
A not matched
status is correct in both cases, is a way to inform the user that at least the resource was created with no issues. I still think that the second case is different, but perhaps the CLI should be more verbose about it ("the connector will not be configured until a site is created") and also it should not wait for a given status.
Describe the bug After creating a connector the
STATUS
field (the one that is printed) is not populated. The fields related with the conditions are populated correctly.How To Reproduce Steps to reproduce the behavior: 1- create a connector 2- check its status with kubectl or the CLI.
Expected behavior If the connector was created successfully it should show "OK" on the status field.
Additional context