build(deps): bump github.com/go-resty/resty/v2 from 2.17.1 to 2.17.2 in the meraki group across 1 directory

[dependabot]

Bumps the meraki group with 1 update in the / directory: github.com/go-resty/resty/v2.

Updates github.com/go-resty/resty/v2 from 2.17.1 to 2.17.2

Release notes

Sourced from github.com/go-resty/resty/v2's releases.

v2.17.2

Release Notes

Backport

• backport: header deepcopy fix by @​jeevatkm in go-resty/resty#1110

Release

• release: version bump to v2.17.2 and readme update by @​jeevatkm in go-resty/resty#1112

Full Changelog: go-resty/resty@v2.17.1...v2.17.2

Commits

• b1b3aaa release: version bump to v2.17.2 and readme update (#1112)
• fb4a091 backport: header deepcopy fix (#1110)
• See full diff in compare view

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @dependabot[bot]? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 91212959-684e-4954-970b-19c0525d2585

📥 Commits

Reviewing files that changed from the base of the PR and between c828da9 and 2ab42fe.

📒 Files selected for processing (1)

• NOTICE.txt

✅ Files skipped from review due to trivial changes (1)

• NOTICE.txt

---

📝 Walkthrough

Walkthrough

The pull request updates the github.com/go-resty/resty/v2 dependency from v2.17.1 to v2.17.2. The go.mod entry for that module was changed accordingly, and the NOTICE.txt reference to the module’s license file was updated to reflect the new version. No other module requirements, directives, or exported/public declarations were modified.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/go_modules/main/meraki-4e4938d4bd

• 🛠️ Update Documentation: Commit on current branch
• 🛠️ Update Documentation: Create PR

---

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

[github-actions]

TL;DR

The Buildkite failure is isolated to winlogbeat/eventlog on Windows and does not match this PR’s resty dependency bump. The failing test (TestWindowsEventLogAPI) aborts with Access is denied. when opening the test event source.

Remediation

• Re-run the failing Windows job first (this looks like an environment/permission-sensitive test failure outside the changed files).
• If it reproduces, harden winlogbeat/eventlog/wineventlog_test.go by handling access-denied setup failures explicitly (for example, skip with a clear message when event source creation/open is blocked on the worker image).

Investigation details

Root Cause

The failure occurs in Winlogbeat test setup while creating/opening a Windows Event Log source, not in dependency-resolution or resty call paths.

• Failing callsite: winlogbeat/eventlog/wineventlog_test.go:336-341
  • log, err = eventlog.Open(source)
  • t.Fatal(err) on error
• PR changes are only dependency metadata updates (go.mod, go.sum, NOTICE.txt), with no winlogbeat code changes.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/45371
• Job/step: Winlogbeat: Win 2025 Unit Tests (beats-winlogbeat build 28728)
• Key log excerpt:
  • === FAIL: winlogbeat/eventlog TestWindowsEventLogAPI (0.08s)
  • wineventlog_test.go:341: Access is denied.

Verification

• Not run locally: this runner is Linux, and the failing test path is Windows-specific (eventlog API).

Follow-up

If this starts recurring on Win 2025 workers, consider making setup failures deterministic in test output (explicit skip reason on permission denial) to reduce false-red CI for dependency-only PRs.

---

What is this? | From workflow: PR Buildkite Detective

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

[dependabot]

Looks like github.com/go-resty/resty/v2 is no longer updatable, so this is no longer needed.