Unify the way how we read configuration in Enceladus
Ouverte
Conformance
feature
priority: low
refactoring
Standardization
under discussion
- Langage dominant
- Scala
- Étoiles
- 33
- Forks
- 16
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
## Background
The way how application configuration is read in `spark-job.jar` is a mess. Sometimes it's our own `ConfigReader` sometimes the typesafe config. There are same functions defined for it, sometimes as implicits sometimes as locla ones. Needs some unification
## Feature
Refactor the code to use only `ConfigReader` to access application configuration.
The only exception being Hypedrive plugin, where it's to be considered.
Guide de contribution
Ouvrir le guide de contribution
Évaluation
Cette issue n'a pas encore été évaluée.