Bump scality/vault from 7.89.0 to 7.90.0 in /env/default

[dependabot]

Bumps scality/vault from 7.89.0 to 7.90.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Dependency Bump Evaluation

Version change: scality/vault 7.89.0 -> 7.90.0 (minor)
Semver bump type: minor

Changes:

• Docker image tag bump for scality/vault in the e2e test environment configuration (env/default/values.yaml)
• Release notes unavailable (vault repository not accessible)

Breaking changes: Unable to verify — vault repo is not accessible for release notes or commit history review. However, this is a minor bump, suggesting additive changes only.

Security concerns: None identified. Vault is an internal Scality component used as IAM infrastructure in the e2e test environment. No new transitive dependencies introduced (Docker image swap).

Impact on codebase:

• Vault is not referenced in production code (pkg/) — only in e2e test infrastructure
• Single file changed: env/default/values.yaml (image tag only)
• Vault is referenced in e2e test comments (suite_test.go, replication_test.go) but no code-level integration changes needed
• The e2e tests themselves serve as the compatibility validation for this bump

CI status: IN_PROGRESS — e2e tests and build are still running. These must pass to confirm compatibility.

Recommendation: REVIEW REQUIRED

Notes: This is a low-risk change scoped entirely to the e2e test environment. The vault repo is not accessible, so release notes and commit history could not be reviewed. Once CI passes (especially e2e tests which exercise the vault integration), this should be safe to merge. Will approve once CI is green.

— Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.75%. Comparing base (ea793aa) to head (25ac877).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #194   +/-   ##
=======================================
  Coverage   76.75%   76.75%           
=======================================
  Files          22       22           
  Lines        1957     1957           
=======================================
  Hits         1502     1502           
  Misses        364      364           
  Partials       91       91           

Flag	Coverage Δ
unit	76.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.