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

Filebeat: Run check/update is failing due to a code bug: filebeat/beater/filebeat.go references b.Paths, but *beat.Beat no longer has a Paths field. Update that callsite to use b.Info.Paths, then re-run the failing job.

Remediation

• In filebeat/beater/filebeat.go:498, replace b.Paths with b.Info.Paths in the autodiscover.NewAutodiscover(...) call.
• Re-run make -C filebeat check update (or the Buildkite Filebeat: Run check/update step) to confirm go vet ./... passes.

Investigation details

Root Cause

The failing step is a direct compile/vet failure in Filebeat code, not an infra timeout:

• filebeat/beater/filebeat.go:498 currently passes b.Paths.
• libbeat/beat/beat.go:59-91 defines type Beat struct and it does not include a Paths field.
• Path data is on Beat.Info.Paths (libbeat/beat/info.go:49).

Evidence

• Build: https://buildkite.com/elastic/beats/builds/44313
• Job/step: Filebeat: Run check/update
• Key log excerpt (/tmp/gh-aw/buildkite-logs/filebeat-filebeat-run-checkupdate.txt:133-141):
  • beater/filebeat.go:498:6: b.Paths undefined (type *beat.Beat has no field or method Paths)
  • vet: beater/filebeat.go:498:6: b.Paths undefined (type *beat.Beat has no field or method Paths)
  • Error: failed running go vet ... running "go vet ./..." failed with exit code 1

Verification

• Additional local verification not run in this workflow; diagnosis is based on the Buildkite failure log and matching source definitions above.

Follow-up

This PR only bumps resty in go.mod/go.sum plus NOTICE.txt; the failing Filebeat source file is outside that diff. If this is fixed in a newer base commit, rebasing the PR may also resolve it.

---

What is this? | From workflow: PR Buildkite Detective

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