Repository navigation
First-class support for class-based reconcilers. #1098
Description
Activity
Can we add that to the optional stuct?
Or!! How about allow a options filter function callback to be passed back!!
I think what I suggest above is harder to hold wrong because it requires a different signature iff it is class-based. I think adding stuff to the options struct that is only used for class-based stuff gets confusing (what if I specify it when I'm not using a class-based type?!?).
ok I like the args idea. I will give it a try
/assign
/area API
/kind bug
/kind feature
There is a bug today with
// +genreconciler-based reconcilers that using finalizers and are class-based. Essentially we have no way to keep the wrong class' reconciler from adding finalizers to resources they shouldn't handle or (worse!) removing them from resources they shouldn't handle.We know in general which resources we define are going to be class-based, so my recommendation here would be to adopt the following solution.
The idea here is that we would tell the codegen infrastructure the name of the class annotation. This would then influence the code-generator to add an additional argument to the appropriate constructors: