-
Notifications
You must be signed in to change notification settings - Fork 158
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
Refactor ActionSet Reconciliation Mechanism #1364
Comments
10 tasks
This issue is marked as stale due to inactivity. Add a new comment to reactivate it. |
🚀 |
I have a patch for this; will see if I can break it up into smaller chunks. |
This issue is marked as stale due to inactivity. Add a new comment to reactivate it. |
This issue is closed due to inactivity. Feel free to reopen it, if it's still relevant. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following #1297 (comment), it is becoming harder to reason about the multiple places where the actionset
Status.State
are set andreconcile.ActionSet()
are called, within thecontroller.runAction()
method.We should look into refactoring these code, with the following changes:
i. Call
reconcile.ActionSet()
just once. Right now we try to reconcile the actionset in every iteration of the for loopi. Within the same
for
loop, we store only the state of each phase in memory. The state of the actionset should be set only once per the next bullet pointi. Set
as.Status.State
andas.Status.ErState.Error
only once, based on whethercoreErr
anddeferErr
are nil or not. It feels like because we are setting them in different places, we need to have some "final overrides" in thecontroll.errenderActionsetArtifacts()
method.How to test:
This diff conveys the scope and goal of the refactoring effort:
The text was updated successfully, but these errors were encountered: