iamolegga/enviper

Consider environment variables while unmarshaling viper's config

Here is a list of my own open source projects:

NestJS

nestjs-pino

Platform agnostic logger for NestJS based on pino with request context in every log.

---

nestjs-session

Idiomatic session module for NestJS. Built on top of express-session.

---

nestjs-cookie-session

Idiomatic cookie session module for NestJS. Built on top of cookie-session.

---

nestjs-roles

Type safe roles guard and decorator made easy.

---

nestjs-injectable

@Injectable() on steroids that simplifies work with inversion of control in your hexagonal architecture.

---

nest-ratelimiter

Distributed consistent flexible NestJS rate limiter based on Redis.

---

create-nestjs-middleware-module

Create a simple idiomatic NestJS module based on Express/Fastify middleware in just a few lines of code with routing out of the box.

---

nestjs-configure-after

Declarative configuration of NestJS middleware order.

---

nestjs-saga

Basic implementation of saga pattern for NestJS (do not confuse it with the built-in sagas).

---

nestjs-gcp-pubsub

The most basic and unopinionated implementation of GCP PubSub transport for NestJS microservices.

---

nest-nsq-transport

The most basic and unopinionated implementation of NSQ transport for NestJS microservices.

React Native

react-native-launch-arguments

Get launch arguments for testing with Detox and Appium.

Go

enviper

Consider environment variables while unmarshaling viper's config.

---

rebus

Type-safe bus generator for go.

---

ratelimiter

Rate limiter with sliding window algorithm implementation.

enviper's Issues

Enable support of unmarshaling maps from env variables without config file

In tests uncomment this line and make it work 😅

CVE-2020-26160 vunerability

Dependency graph to the vulnerable library:
github.com/spf13/[email protected] -> github.com/dgrijalva/[email protected]+incompatible

upgrading to the latest viper would fix this.

Pointers not being mapped correctly with only ENV variables

Hi,

First thanks for the contribution.
I'm checking this package becase I've experienced the issue with viper, however seems like the example you provide in the documentation does not work as expected when there's no configuration file that fills values for pointers and maps.

If I execute the example without any config file (just adding environment values) the value for Barries map[string]barry and Quxxy *quxxy is allways nil. I have pushed some code in a personal repo to illustrate this issue: https://github.com/afdecastro879/enviper-test If you run the main program you will find that I'm setting the environment variables like this:

	os.Setenv("FOO", "foo")
	os.Setenv("BARRY_BAR", "42")
	os.Setenv("BAZ", "true")
	os.Setenv("BARRIES_KEY1_BAR", "42")
	os.Setenv("QUXXY_QUX", "ipsum")

But when printing the struct the result for the values explained above are nil:

main.config{Foo:"foo", Barry:main.barry{Bar:42}, Barries:map[string]main.barry(nil), Bazzy:main.bazzy{Baz:true}, Quxxy:(*main.quxxy)(nil)}

Log a warning or return an error from `Unmarshal()` if a non-bindable environment variable is present.

Probably is only useful when the prefix is set.

type config struct {
    Bar string
}

func main() {    
    var c config
    e := enviper.New(viper.New())
    e.SetEnvPrefix("MYAPP")
	os.Setenv("MYAPP_BAZ", "1")
	e.Unmarshal(&c) // warning: MYAPP_BAZ is non-bindable
}

Enable support for maps with as value primitive types

Currently, only maps with as value a struct are supported.
If you try using the following map it will crash:
map[string]string

To make this function you need to use a map[string]struct{ Value string }.

Example to reproduce the issue

e := enviper.New(viper.New())
e.AddConfigPath(".")
e.SetConfigName("config")

var cfg struct {
    Fields map[string]string
}

if err := e.Unmarshal(cfg); err != nil {
    panic("unable to decode into config struct")
}

[Fields]
key1="value1"

e.VIper.ReadInConfig run as part of Unmarshal clears merged in fields

Hi,

due to e.Viper.ReadInConfig() that is invoked as part of Enviper#Unmarshal any additional fields added via Viper#MergeConfigMap method are cleared. That prevents usage like that:

        e := enviper.New(viper.New())
	if err := e.ReadInConfig(); err != nil {
		panic(err.Error())
	}
	if err := e.MergeConfigMap(defaults.AllSettings()); err != nil {
		panic(err.Error())
	}
	if err := e.Unmarshal(&cfg); err != nil {
		panic(err.Error())
	}

Is there a reason why Unmarshal makes a call to ReadInConfig? Afaik, viper itself expects users to call ReadInConfig explicitly before Unmarshal is used