Skip to content

Add dataset access control for model configurations#81

Open
ericc59 wants to merge 2 commits intomainfrom
feature/dataset-access-control
Open

Add dataset access control for model configurations#81
ericc59 wants to merge 2 commits intomainfrom
feature/dataset-access-control

Conversation

@ericc59
Copy link
Copy Markdown
Collaborator

@ericc59 ericc59 commented Feb 3, 2026

Summary

  • Add datasets field to models.yml for controlling which datasets a model can access
  • Default to ["public-v1", "public-v2"] only; private datasets require explicit opt-in
  • Add get_allowed_datasets() and is_dataset_allowed() utilities in task_utils.py
  • Add cli/check_dataset.py for validating dataset access from shell scripts

Dataset Configuration

Models without a datasets field default to public datasets only:

datasets: ["public-v1", "public-v2"]  # DEFAULT if not specified

To allow private datasets, add explicit configuration:

datasets: ["public-v1", "public-v2", "private-v1", "private-v2"]

Test plan

  • Verify cli/check_dataset.py returns exit code 0 for allowed datasets
  • Verify cli/check_dataset.py returns exit code 1 for disallowed datasets
  • Verify models without datasets field default to public only

- Add 'datasets' field to models.yml for controlling which datasets a model can access
- Default to public-v1 and public-v2 only; private datasets require explicit opt-in
- Add get_allowed_datasets() and is_dataset_allowed() utilities in task_utils.py
- Add cli/check_dataset.py for validating dataset access from shell scripts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant