fix: Add project filter to apply_data_source and delete_data_source (closes #6206) by mailtoboggavarapu-coder · Pull Request #6322 · feast-dev/feast

…ixes feast-dev#6206)

Filters existing data sources by both name and project in the file
registry implementation, fixing cross-project contamination (issue feast-dev#6206).

Changes:
- apply_data_source: added project-scoped deduplication check
- delete_data_source: added project filter to avoid cross-project deletion

Signed-off-by: Venkateswarlu Boggavarapu <mailtoboggavarapu@gmail.com>

Regression tests for feast-dev#6206:
- test_apply_data_source_cross_project_isolation: verifies applying a data
  source to project_a does not overwrite the same-named source in project_b
- test_delete_data_source_project_scoped: verifies delete_data_source only
  removes the source from the specified project

Signed-off-by: Venkateswarlu Boggavarapu <mailtoboggavarapu@gmail.com>

Signed-off-by: Venkateswarlu Boggavarapu <mailtoboggavarapu@gmail.com>

Changed parametrize decorators from all_fixtures to [lazy_fixture("local_registry")] for
both new test functions to avoid polluting the session-scoped sqlite_registry fixture.

Signed-off-by: Venkateswarlu Boggavarapu <mailtoboggavarapu@gmail.com>