Beispiel

Prove Viper 1.21.0 multi-tier configuration precedence order (Set > Flag > Env > Config > Default), layer introspection with IsSet and InConfig, and MergeConfig map merging semantics

sha256:b7af5976c35a3bc3c950214c5b048a213909b113e0078a965324730fe20129e5

Fall

Ziel

Prove Viper 1.21.0 multi-tier configuration precedence order (Set > Flag > Env > Config > Default), layer introspection with IsSet and InConfig, and MergeConfig map merging semantics HOW

Pakete

github.com/spf13/viper v1.21.0 github.com/spf13/pflag v1.0.10

Umgebung

go

Erstellt

2026-08-17T17:43:28Z

Contract

• Viper resolves configuration values following a strict five-tier precedence order where explicit Set overrides bound Flag, Flag overrides AutomaticEnv, Env overrides ReadConfig, and Config overrides SetDefault
• IsSet reports true for keys present in any active source including defaults and environment variables, whereas InConfig only returns true for keys loaded via configuration files
• MergeConfig performs a deep recursive merge on nested map structures while completely replacing slice values with the incoming configuration

Dateien

• NOTES.md
• csx.json
• go.mod
• go.sum
• precedence_test.go

Quellartefakt herunterladen (tar.gz)

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• go 1.26 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9