chore(evalhub): sync provider ConfigMaps from upstream eval-hub raw

[gnaulak-redhat]

Sync eval-hub/eval-hub main config provider yaml files.
These files are auto-synced with hack/sync-evalhub-providers.py script

This is in part to fix the ci pipeline in eval-hub/eval-hub repository side

Run python scripts/check_configmap_sync.py
Fetching ConfigMap listing from trustyai-explainability/trustyai-service-operator...
Found 9 ConfigMap(s) to check.

OK  collection-leaderboard-v2.yaml <-> config/collections/leaderboard-v2.yaml
OK  collection-safety-and-fairness-v1.yaml <-> config/collections/safety-and-fairness-v1.yaml
OK  collection-toxicity-and-ethical-principles.yaml <-> config/collections/toxicity-and-ethical-principles.yaml

Drift detected:

provider-garak-kfp.yaml vs config/providers/garak-kfp.yaml:
  ~ runtime.local.command: remote='true'  local='python tests/features/test_data/runtime/main.py'
provider-garak.yaml vs config/providers/garak.yaml:
  ~ runtime.local.command: remote='true'  local='python tests/features/test_data/runtime/main.py'
provider-guidellm.yaml vs config/providers/guidellm.yaml:
  ~ runtime.local.command: remote='true'  local='python tests/features/test_data/runtime/main.py'
provider-ibm-clear.yaml vs config/providers/ibm-clear.yaml:
  ~ runtime.local.command: remote='true'  local='python tests/features/test_data/runtime/main.py'
provider-lighteval.yaml vs config/providers/lighteval.yaml:
  ~ runtime.local.command: remote='true'  local='python tests/features/test_data/runtime/main.py'
provider-lm-evaluation-harness.yaml vs config/providers/lm_evaluation_harness.yaml:
  ~ runtime.local.command: remote='true'  local='python tests/features/test_data/runtime/main.py'
Error: Process completed with exit code 1.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

Warning

Rate limit exceeded

@gnaulak-redhat has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 26 minutes and 34 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7ffcf257-8241-4774-9637-c6ef13e19dec

📥 Commits

Reviewing files that changed from the base of the PR and between 8ea0718 and fe89ce5.

📒 Files selected for processing (10)

• config/configmaps/evalhub/collection-leaderboard-v2.yaml
• config/configmaps/evalhub/collection-safety-and-fairness-v1.yaml
• config/configmaps/evalhub/collection-toxicity-and-ethical-principles.yaml
• config/configmaps/evalhub/provider-garak-kfp.yaml
• config/configmaps/evalhub/provider-garak.yaml
• config/configmaps/evalhub/provider-guidellm.yaml
• config/configmaps/evalhub/provider-ibm-clear.yaml
• config/configmaps/evalhub/provider-lighteval.yaml
• config/configmaps/evalhub/provider-lm-evaluation-harness.yaml
• hack/sync-evalhub-providers.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

@gnaulak-redhat: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/trustyai-service-operator-e2e	fe89ce5	link	true	/test trustyai-service-operator-e2e

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.