spotify/scio

Consider using another configuration mechanism other than properties

Open

#1,497 opened on Nov 1, 2018

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Scala (529 forks)auto 404
good first issuequestion ❓

Repository metrics

Stars
 (2,626 stars)
PR merge metrics
 (PR metrics pending)

Description

It seems like scio uses System Properties for some configurations.

Motivated by reasons listed here https://medium.com/@hussachai/configurations-are-you-doing-it-wrong-e4ea2672a4a9 , I would like to ask whether we should consider supporting configuration via another mechanism.

Contributor guide

Research direction
Investigate current usage of System Properties in scio, especially in scio extra and PropertySpec. Evaluate alternative configuration mechanisms such as environment variables, configuration files (e.g., HOCON), or dependency injection. Propose a migration plan that maintains backward compatibility. Look at similar libraries like Apache Beam itself or other Scala data processing frameworks for best practices.
Tech stack
scala
Domain
backenddevops
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.
1-2 days
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
ScalaApache Beam
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40