chore(deps): bump github.com/elastic/go-ucfg from 0.9.1 to 0.9.2

[dependabot]

Bumps github.com/elastic/go-ucfg from 0.9.1 to 0.9.2.

Release notes

Sourced from github.com/elastic/go-ucfg's releases.

v0.9.2

What's Changed

• Bump the github-actions group across 2 directories with 1 update by @​dependabot[bot] in elastic/go-ucfg#228
• Bump the github-actions group across 2 directories with 1 update by @​dependabot[bot] in elastic/go-ucfg#230
• Fix panic with empty name and negative index by @​lorienhu in elastic/go-ucfg#232
• Update CHANGELOG.md for v0.9.2 release by @​lorienhu in elastic/go-ucfg#233

New Contributors

• @​lorienhu made their first contribution in elastic/go-ucfg#232

Full Changelog: elastic/go-ucfg@v0.9.1...v0.9.2

Changelog

Sourced from github.com/elastic/go-ucfg's changelog.

[0.9.2]

Fixed

• Return an error instead of panicking when config access uses an empty field name together with a negative index. #232

Commits

• 96d3af5 Add missing 0.9.1 entries and new 0.9.2 release notes. (#233)
• a364c67 Return error for empty path and -1 index (#232)
• e846366 Bump the github-actions group across 2 directories with 1 update (#230)
• c991c6f Bump the github-actions group across 2 directories with 1 update (#228)
• See full diff in compare view

[infra-vault-gh-plugin-prod]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: 76d297f

Failed CI Steps

• Check integrations amazon_security_lake
• Check integrations amazon_security_lake
• Check integrations cloudflare_logpush
• Check integrations sentinel_one_cloud_funnel
• Check integrations sentinel_one_cloud_funnel

History

• 💔 Build #49609 failed 5c4ad69
• 💔 Build #49601 failed 5db958f

[github-actions]

TL;DR

Both failed Buildkite steps (amazon_security_lake and sentinel_one_cloud_funnel) exited with status 1, but the prefetched logs for this run only contain teardown/artifact-upload output and do not include the actual first failing assertion/error. Immediate next action is to open each step’s full raw log (or JUnit XML) and capture the earliest failure line before attempting a code change.

Remediation

• Retrieve the full failing section for each step (from the Buildkite step raw log or build/test-results/* artifacts), specifically the first FAIL/error before stack teardown starts.
• After the concrete error is visible, map it to source and fix accordingly; if the logs still contain only teardown data, re-run the build once to rule out log collection/transient infrastructure issues.

Investigation details

Root Cause

Current evidence is inconclusive for both failed jobs because the available logs are missing the failure body and only show post-failure teardown.

• /tmp/gh-aw/buildkite-logs/integrations-check-integrations-amazon_security_lake.txt shows only:
  • --- [amazon_security_lake] failed
  • 🚨 Error: The command exited with status 1
  • stack cleanup and artifact upload
• /tmp/gh-aw/buildkite-logs/integrations-check-integrations-sentinel_one_cloud_funnel.txt shows only:
  • --- [sentinel_one_cloud_funnel] failed
  • 🚨 Error: The command exited with status 1
  • stack cleanup and artifact upload

No assertion, panic, compile/type error, or dependency-resolution error is present in the provided excerpts, so a reliable category (code bug / test failure / dependency issue / infrastructure / configuration) cannot be assigned yet without additional log content.

PR scope check: #21237 changes only go.mod/go.sum (github.com/elastic/go-ucfg 0.9.1 → 0.9.2), which does not by itself identify which package-level test failed.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/49656
• Failed jobs:
  • Check integrations amazon_security_lake
  • Check integrations sentinel_one_cloud_funnel
• Key available log lines (both logs):
  • 🚨 Error: The command exited with status 1
  • followed by artifact upload and Elastic stack teardown only

Verification

• Not run locally (analysis based on prefetched Buildkite artifacts for this detective run).

Follow-up

• Please share either:
  • full raw log excerpt from each failed step starting at the first error, or
  • the corresponding build/test-results/*.xml failure blocks.

With that, I can provide a precise root-cause classification and patch-level remediation.

---

What is this? | From workflow: PR Buildkite Detective

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