Jason Parraga
Should be good for another look @pvditt
The end2end test is failing but I've tested this in a development environment without issues hmm.
@machichima this one wasn't ready for review yet since I was trying to work out the build failure. I'll circle back later.
> From reading you description it sees expired at is a better primary key member Yeah that would work as well. Just need to widen that composite key with something.
> A little gift to help with this: our fork of mockery has just been [removed](https://github.com/flyteorg/flyte/pull/6280). Much appreciated thank you
> Can we separate the move to go 1.23 from the bump in mockery version? Since moving to this new version is non-controversial, how about we do it separately (either...
> Can we separate the move to go 1.23 from the bump in mockery version? Since moving to this new version is non-controversial, how about we do it separately (either...
> So I'm having trouble because it seems that the mockery libraries are tightly coupled with a very specific version of go. When I use the version of mockery that...
> Can we separate the move to go 1.23 from the bump in mockery version? Since moving to this new version is non-controversial, how about we do it separately (either...
This may be related: https://github.com/kubernetes-sigs/kustomize/issues/4713