[V2] Move validation to a validation function

[machichima]

I'm thinking of moving this to a validation function, as well as validating other fields in taskAction, and put this validation function before we add the finalizer. In this case, if the validation failed, we can just not requeue it, and do not need to remove the finalizer.

We can do this in follow-up!

Originally posted by @machichima in #6903 (comment)

[runllm]

Moving validation logic to a dedicated validation function for taskAction is a recommended approach, as it allows you to validate all necessary fields before adding the finalizer. This ensures that if validation fails, the object is not requeued and the finalizer does not need to be removed, simplifying error handling and improving code maintainability. This pattern is discussed in the referenced PR review and aligns with best practices for controller logic in Flyte's codebase, though the specific implementation details are not present in the data sources—only the general approach is mentioned in the PR discussion itself.

Would you like more detail on how to implement such a validation function or examples from Flyte's codebase?

Sources:

• Flyte PR #6903 review comment

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!