rename aws key

[shanyl9]

Summary by CodeRabbit

• Refactor
  • Updated account identifier metadata key naming to align with system conventions, ensuring consistent account references across the platform.
• Chores
  • Bumped an internal dependency to a newer version for ongoing maintenance and compatibility.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 760ee2be-f562-4f02-9783-3e0e77d319b1

📥 Commits

Reviewing files that changed from the base of the PR and between 87bba79 and ad24796.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (2)

• go.mod
• instanceidhandler/v1/helpers/keys.go

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

• go.mod

🚧 Files skipped from review as they are similar to previous changes (1)

• instanceidhandler/v1/helpers/keys.go

---

📝 Walkthrough

Walkthrough

The PR renames an exported metadata constant from AWS-specific AWSAccountIDMetadataKey (kubescape.io/aws-account-id) to cloud-agnostic CloudAccountIdentifierMetadataKey (kubescape.io/cloud-account-identifier) and updates the github.com/armosec/armoapi-go dependency version in go.mod.

Changes

Cohort / File(s)	Summary
Metadata Key Constant Update instanceidhandler/v1/helpers/keys.go	Renamed exported constant AWSAccountIDMetadataKey → CloudAccountIdentifierMetadataKey and changed its string value from kubescape.io/aws-account-id to kubescape.io/cloud-account-identifier.
Dependency Bump go.mod	Updated module requirement github.com/armosec/armoapi-go from v0.0.667 to v0.0.693.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• matthyx

Poem

🐰 A nibble, a rename, a hop so light,
Cloud keys now wander beyond AWS night.
One constant reborn, broad skies in view,
Hopping through metadata, fresh and new! 🌤️

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'rename aws key' is directly related to the main change: renaming AWSAccountIDMetadataKey to CloudAccountIdentifierMetadataKey, but it oversimplifies the scope by not mentioning the broader shift from AWS-specific to cloud-agnostic naming.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rename_aws_keys

📝 Coding Plan

• Generate coding plan for human review comments

---

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.}

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success