awslabs / awslabs/amazon-redshift-utils
Support local config file in WorkloadManagementScheduler
- Dominant language
- Python
- Stars
- 2.8k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
**Feature Request**
In [WorkloadManagementScheduler/wlm_scheduler.py](https://github.com/awslabs/amazon-redshift-utils/blob/7d2361b96b9599d9a47a593d18c4b12f832f9a38/src/WorkloadManagementScheduler/wlm_scheduler.py)
Currently both inplace configuration and json files stored in s3 are supported.
Additionally add support for local json file stored in lambda's code dir.
https://github.com/awslabs/amazon-redshift-utils/blob/7d2361b96b9599d9a47a593d18c4b12f832f9a38/src/WorkloadManagementScheduler/wlm_scheduler.py#L98-L105
Contributor guide
Research direction
Start in src/WorkloadManagementScheduler/wlm_scheduler.py, especially the configuration handling around lines 98-105. Trace how inline configuration and S3 JSON files are selected, then check the Lambda code directory behavior. Done means a local JSON configuration is accepted alongside the existing sources and the relevant scheduler tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 62/100