-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Migrate AWS SDK in CCM AWS to v2
-
Product / Portfolio Work
-
-
0% To Do, 0% In Progress, 100% Done
-
False
-
-
False
-
Not Selected
-
XS
-
None
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
- As AWS is planning to end support for AWS SDK v1, the Go AWS SDK v1 that CCM AWS currently use will no longer be getting any sort of updates in July. We need to upgrade to the new SDK in order to stay supported. More read: https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/
- All the files using AWS SDK v1: https://github.com/search?q=repo%3Akubernetes%2Fcloud-provider-aws+github.com%2Faws%2Faws-sdk-go%2F&type=code
Why is this important?
- …
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
- clones
-
OCPCLOUD-2964 Migrate AWS SDK in MAPI AWS to v2
-
- Closed
-