If we encounter a problem during an async operation, we report it in the AsyncOperation condition. However, this informs user about only the last operation error like the following:
If user fixes the error and then the apply operation for example continues successfully, the error is still there until that operation finishes and users don't have a clear way of knowing that they fixed the problem.
How could Terrajet help solve your problem?
We cannot re-use the same condition to notify about the new operation because that would mean deleting the error in every reconcile and writing a new one. So, we need a way to let the user know that there is a new operation begun since the last error we show.
What problem are you facing?
If we encounter a problem during an async operation, we report it in the
AsyncOperation
condition. However, this informs user about only the last operation error like the following:If user fixes the error and then the
apply
operation for example continues successfully, the error is still there until that operation finishes and users don't have a clear way of knowing that they fixed the problem.How could Terrajet help solve your problem?
We cannot re-use the same condition to notify about the new operation because that would mean deleting the error in every reconcile and writing a new one. So, we need a way to let the user know that there is a new operation begun since the last error we show.