aws / aws/eks-anywhere

Refactor machine config validation using config manager validation

Open
#2,089 0 comments 0 reactions 0 assignees View on GitHub
area/providers/capc kind/cleanup team/providers
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

**What would you like to be added**:
This is a code refactor (no feature added/deleted/updated) so that config manager validator can use reflection to call cloud providers that implement validate interface for machine config validation for static validation.

**Why is this needed**:
The refactor can reduce provider's validator.go ValidateClusterMachineConfigs to only have context aware validation.

Contributor guide

Open the contributing guide

Research direction

Start by locating the config manager validator and provider ValidateClusterMachineConfigs implementations mentioned in the issue. Trace how static and context-aware validation are separated, then verify that providers implementing the validate interface are discovered and invoked through the config manager while provider validation retains only context-aware checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
infrastructure
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.