[Refactor] Define all mockery in .mockery.yaml

[machichima]

For places that use //go:generate mockery, we should put into https://github.com/flyteorg/flyte/blob/v2/.mockery.yaml instead.

related to comment: #6813 (comment)

[runllm]

It seems likely that the Flyte project is moving towards centralizing all mockery configuration in the .mockery.yaml file at the root of the repository, rather than using scattered //go:generate mockery directives in individual files. This is supported by the discussion in PR #6813, where a maintainer suggests that mock generation should be defined in .mockery.yaml for consistency and efficiency.

The .mockery.yaml file allows for a unified configuration of mock generation, making it easier to manage and update mocks across the codebase. This approach replaces the need for per-file //go:generate mockery comments and aligns with recent refactoring efforts in the Flyte repository. However, the data sources do not provide the exact contents or structure of the .mockery.yaml file, nor do they detail the migration process for existing //go:generate directives.

Would you like more detail on how to migrate existing mockery directives to .mockery.yaml or on the benefits of this approach?

Sources:

• PR #6813, comment on mockery config

---

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!

[ankitkumarsingh1702]

I've created PR #6877 to address this issue.

Summary of changes:

• Created .mockery.yaml with all mockery definitions organized by package (datacatalog, flytectl, flytepropeller, flytestdlib, flyteplugins, flyteadmin, flyteidl)
• Removed //go:generate mockery comments from 107 Go files across the codebase

The centralized configuration makes it easier to:

1. Manage mock generation settings in one place
2. Modify options without touching source files
3. Maintain consistency across all packages
4. Discover all mocked interfaces at a glance

[machichima]

Hi @ankitkumarsingh1702 ,
This is already solved by #6829. Thank you!