test: catalog-info failure

[v1v]

No description provided.

[github-actions]

TL;DR

The catalog-info workflow failed in validate because catalog-info.yaml contains a misspelled key: povider_settings instead of provider_settings. Rename it back to provider_settings and re-run checks.

Remediation

• In catalog-info.yaml, change povider_settings: back to provider_settings: under the buildkite-pipeline-integrations-test-stack resource.
• Push the fix and re-run the catalog-info workflow (or re-run failed jobs) to confirm schema validation passes.

Investigation details

Root Cause

elastic/oblt-actions/elastic/validate-catalog@v1 runs rre validate --backstage-entity-aware --verbose catalog-info.yaml. The validator rejects an unexpected field path under the Buildkite pipeline spec due to a typo in the key name introduced by this PR.

Evidence

• Workflow: https://github.com/elastic/integrations/actions/runs/25885354579
• Job/step: validate → Run elastic/oblt-actions/elastic/validate-catalog@v1
• Changed line in PR (catalog-info.yaml):
  • provider_settings: → povider_settings:
• Key log excerpt:

Error encountered while validating Resource buildkite-pipeline-integrations-test-stack ✗
1 validation error for RRE
spec.implementation.`buildkite.elastic.dev/v1`.Pipeline.spec.povider_settings
  Extra inputs are not permitted [type=extra_forbidden, ...]
##[error]Process completed with exit code 1.

Validation

• Not run locally in this workflow context (read-only diagnosis from workflow logs and PR diff).

Follow-up

• After correcting the key typo, the same validator step should proceed past this resource without the extra_forbidden schema error.

---

What is this? | From workflow: PR Actions Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.