VPR-74 chore(deps): upgrade AWS SDK from v3 to v4#256
Open
rlorenzo wants to merge 1 commit into
Open
Conversation
- 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 Report✅ All modified and coverable lines are covered by tests. 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
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
Bundle ReportBundle size has no change ✅ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrades the AWS SDK for .NET from v3 to v4 in both projects that reference it (Viper and EffortMigration):
AWSSDK.Core3.7.201.7 -> 4.0.100Amazon.Extensions.Configuration.SystemsManager5.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
/Development+/Sharedparameter sets.Verification
npm run verify:build: 0 errors;npm run test:backend: 2140/2140 passed/health/detailfully Healthy includingaws-ssm(live v4GetParametersByPathcall) and all ninedb-*checks (DB passwords delivered via SSM)AWSSDK.Core 4.0.100.0,SystemsManager 7.1.0.0, and transitiveAWSSDK.SimpleSystemsManagement 4.0.6.11JIRA: https://ucdsvm.atlassian.net/browse/VPR-74