Upgrade to CDK v2
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws, python
- Domain
- cloud, infrastructure
Research direction
Start with the CDK dependency declarations in setup.py at lines 26–37, then inspect the framework for the related CDK v1 usage. Done means the project is adapted to CDK v2 and its existing checks or tests pass with the updated dependency.
Written by the indexing model from the issue text.
Description
Currently, the framework is built against CDK v1:
For the sake of future-proofing, it seems wise to adapt to CDK v2 before the project gets too large.
- Dominant language
- Python
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from developmentseed/ingest-framework
-
Setup linting Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Support versioning Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in developmentseed/ingest-framework
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100