Investigate if performance for reading configuration files can be improved
dominikbraun opened this issue · comments
Currently, verless parses the verless.yml file and unmarshals it into a config.Config instance using viper. Unmarshalling typically isn't the fastest way to do things and we therefore should investigate whether the performance can be improved - for example by just accessing configuration keys like viper.Get("build.overwrite").
It seems like viper.Get has its own pitfalls: spf13/viper#311
Due to the downsides of viper.Get, we won't change how the configuration files are parsed at this time.