-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document Warning State #317
Conversation
Write documentation in which cases Eventing CR state gets Warning state
I understand you that there is little difference. We had different opinions about it, but decided to do like this. I just documented the requirement here what was written in the issue. Unfortunatley this is the way it is. |
ActiveBackend BackendType `json:"activeBackend"` | ||
BackendConfigHash int64 `json:"specHash"` | ||
// Can have one of the following values: Ready, Error, Processing, Warning. Ready state is set | ||
// when all the resources are deployed successfully and backend is connected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this correct right now? It might change together with: #267
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is independen from the issue. The owner of the issue should add more details as the issue is completed, I'd say.
Write documentation in which cases Eventing CR state gets Warning state