Refactor `BuildSpecForCluster` to better account for the growing number of args
Open
area/cli
kind/cleanup
team/cli
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
Refactor `BuildSpecForCluster` to take an interface since the number of arguments is increasing. This will make it easier to add more options here as it continues to grow,
Original post: https://github.com/aws/eks-anywhere/pull/1391#discussion_r821188968
Contributor guide
Research direction
Start by locating the BuildSpecForCluster entry point and inspect its callers to understand the current argument list and the cluster specification flow. Check the related tests, if present, before changing the function boundary; done means the arguments are represented by an interface, callers are updated, and the existing tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100