Skip to content

VPR-74 chore(deps): upgrade AWS SDK from v3 to v4#256

Merged
rlorenzo merged 1 commit into
mainfrom
chore/VPR-74-aws-sdk-v4
Jul 10, 2026
Merged

VPR-74 chore(deps): upgrade AWS SDK from v3 to v4#256
rlorenzo merged 1 commit into
mainfrom
chore/VPR-74-aws-sdk-v4

Conversation

@rlorenzo

@rlorenzo rlorenzo commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Upgrades the AWS SDK for .NET from v3 to v4 in both projects that reference it (Viper and EffortMigration):

  • AWSSDK.Core 3.7.201.7 -> 4.0.100
  • Amazon.Extensions.Configuration.SystemsManager 5.1.0 -> 7.1.0 (the SDK-v4 line)

Core is pinned to 4.0.100 rather than the latest 4.0.100.2, which was published under the 7-day supply-chain bake window at review time; the delta is routine service-model updates and can be picked up in a later bump.

No code changes were needed: our AWS surface (SSM Parameter Store config load, AwsSsmHealthCheck, credential profile registration) uses no APIs removed in v4.

Breaking changes reviewed

  • SDK v4 migration guide: nullable value types, collections defaulting to null, STS/S3/DynamoDB changes - none apply to our usage.
  • SystemsManager extension crosses two majors: 6.0.0 splits StringList parameters into indexed keys; 6.2.0 throws at startup on case-insensitive duplicate parameter keys under a loaded path. Neither affects the current /Development + /Shared parameter sets.

Verification

  • npm run verify:build: 0 errors; npm run test:backend: 2140/2140 passed
  • Booted the app locally: clean startup with config loaded from SSM, /health/detail fully Healthy including aws-ssm (live v4 GetParametersByPath call) and all nine db-* checks (DB passwords delivered via SSM)
  • Confirmed the running process loaded AWSSDK.Core 4.0.100.0, SystemsManager 7.1.0.0, and transitive AWSSDK.SimpleSystemsManagement 4.0.6.11

JIRA: https://ucdsvm.atlassian.net/browse/VPR-74

- AWSSDK.Core 3.7.201.7 -> 4.0.100 and
  Amazon.Extensions.Configuration.SystemsManager 5.1.0 -> 7.1.0 in
  Viper and EffortMigration
- pinned Core to 4.0.100 instead of latest 4.0.100.2, which is under
  the 7-day supply-chain bake window
- crossing extension majors 6 and 7: startup now throws on
  case-insensitive duplicate SSM keys and splits StringList params;
  verified clean against /Development and /Shared
@codecov-commenter

codecov-commenter commented Jul 6, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 45.29%. Comparing base (8991c34) to head (5096a64).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #256   +/-   ##
=======================================
  Coverage   45.29%   45.29%           
=======================================
  Files         897      897           
  Lines       51929    51929           
  Branches     4879     4879           
=======================================
  Hits        23522    23522           
  Misses      27803    27803           
  Partials      604      604           
Flag Coverage Δ
backend 45.39% <ø> (ø)
frontend 43.41% <ø> (ø)

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

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

@codecov-commenter

Copy link
Copy Markdown

Bundle Report

Bundle size has no change ✅

@rlorenzo
rlorenzo requested a review from bsedwards July 10, 2026 20:48
@rlorenzo

Copy link
Copy Markdown
Contributor Author

@bsedwards I thought this would involve a breaking API change since this is a major version, but updating the package works out of the box with no changes needed. Working on the TEST server as well.

@rlorenzo
rlorenzo merged commit 5921cb6 into main Jul 10, 2026
13 of 19 checks passed
@rlorenzo
rlorenzo deleted the chore/VPR-74-aws-sdk-v4 branch July 10, 2026 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants