bcgov / bcgov/parks-data-register
DR: Update AWS SDK to V3
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Description:
Update AWS-SDK from V2 to V3. When using V2 it is fairly common to see warnings about outdated functionality along with a reminder V2 is nearing end of support. This task is go through the process of updating to V3, resolve all the warnings, and test the app to ensure any breaking changes caused from this update have been resolved.
Amazons guide for Updating to V3
Acceptance Criteria:
DATA Register now uses AWS-SDK V3.
Development Checklist:
- all warnings about v2 to v3 have been resolved
- Maintain functionality
- API, Admin now using V3
Dependencies
- Blocked by
- Blocking
Relevant documentation as reference
Definition of Ready
- Acceptance criteria are included
- Wireframes are included (if applicable)
- Design / Solution is accepted by Product Owner (if applicable)
- Dependencies are identified (technical, business, regulatory/policy)
- Story has been estimated (under 13 pts)
Definition of Done
- In progress:
- Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- UI meets accessibility requirements
- Unit tests are written
- Work is traceable in GitHub
- PR linked to ticket number
- If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
- Code review:
- Code is peer reviewed and has passed CI/CD tests
- QA:
- Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- Code is potentially shippable to the production environment
- Functional features have been tested and passed by QA
- UI components tested by designer
- Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
- PO Review:
- Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- Reviewed and approved by Product Owner
Notes:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the AWS SDK v2 usages in the repository and reviewing the API and Admin areas named in the issue. Use Amazon's V2-to-V3 migration guide and run the existing application tests. Done means DATA Register uses AWS SDK V3, migration warnings are resolved, existing functionality is maintained, and the API and Admin paths are tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- api, backend, cloud
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100