kedacore/keda

Refactor scalers parsing to unify them

Open

#5,037 opened on Oct 1, 2023

View on GitHubContributor guide
 (12 comments) (3 reactions) (0 assignees)Go (1,457 forks)auto 404
feature-requesthelp wantedneeds-discussionstale-bot-ignore

Repository metrics

Stars
 (10,372 stars)
PR merge metrics
 (PR metrics pending)

Description

Proposal

Currently, each scaler parses the configuration using its own way, some of them use helpers for reading envs, other don't, some use one helper, others use their own helpers... There is a lot of fragmentation in scalers code and we should unify it

Use-Case

No response

Is this a feature you are interested in implementing yourself?

Maybe

Anything else?

No response

Contributor guide

Research direction
Analyze the existing scaler configuration parsing implementations across different scalers. Identify common helpers or patterns used, and propose a unified approach that standardizes parsing, possibly by creating a shared utility or interface. Look at the codebase for examples of scalers with different parsing styles and document the discrepancies.
Tech stack
go
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoKubernetesKEDA scalers
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50