Skip to content

feat: migrate to new golang-commons config API (#81)#84

Merged
makdeniss merged 2 commits intomainfrom
feat/migrate-goland-commons-config
Mar 6, 2026
Merged

feat: migrate to new golang-commons config API (#81)#84
makdeniss merged 2 commits intomainfrom
feat/migrate-goland-commons-config

Conversation

@makdeniss
Copy link
Contributor

  • Migrate to the new golang-commons config API.
  • Replace legacy Viper-based config binding (NewDefaultConfig(rootCmd) + BindConfigToFlags) with explicit constructor/flags wiring.
  • Keep existing CLI defaults and flag names to preserve current behavior.

@makdeniss makdeniss self-assigned this Mar 5, 2026
@makdeniss makdeniss added the enhancement New feature or request label Mar 5, 2026
@makdeniss makdeniss marked this pull request as ready for review March 5, 2026 08:04
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not the biggest fan of having these config tests. They test flag parsing behavior is testing golang internals

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to follow the existing approaches. And I've also seen that Bastian added them if they were missing: https://github.com/platform-mesh/extension-manager-operator/pull/635/changes

@makdeniss makdeniss requested a review from aaronschweig March 6, 2026 08:18
@makdeniss makdeniss merged commit aa524e6 into main Mar 6, 2026
12 checks passed
@makdeniss makdeniss deleted the feat/migrate-goland-commons-config branch March 6, 2026 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request feature

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants