Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

KumuluzEE Go Config

KumuluzEE Go Config is an open-source configuration management for the KumuluzEE framework. It is a Go package based on KumuluzEE Config, configuration management library developed for microservices written in Java programming language. It extends basic configuration framework described here.

Package provides support for environment variables and configuration files as well as for additional configuration sources Consul and etcd.

KumuluzEE Go Config follows the idea of an unified configuration API for the framework and provides additional configuration sources which can be utilised with a standard KumuluzEE configuration interface.


You can go get this package:

$ go get


In order to connect to Consul and etcd, you must properly set configuration files. For more information check sections Configuring Consul and Configuring etcd in KumuluzEE Config's section Usage.

Properties in Consul and etcd are stored in a specific matter. For more information check sections Configuration properties inside Consul and Configuration properties inside etcd in KumuluzEE Config's section Usage.

Configuration source priorities

Each configuration source has its own priority, meaning values from configuration sources with lower priories can be overwritten with values from higher. Properties from configuration files has the lowest priority, which can be overwritten with properties from additional configuration sources (i.e. Consul or etcd), while properties defined with environmental variables have the highest priority.


Properties can be held in a struct using config.Bundle or retrieved by using config.Util methods.


config.NewBundle(prefixKey, fields, options)

prefixKey (string): value represents the prefix key for the configuration property keys use "" (empty string) for no prefix.

fields (struct pointer): struct that will be populated with configuration properties. Fields in the struct that will be populated must be exported (starting with an upper-case letter). By default, configuration key is equal to field name, but with first letter lower-cased. Fields can use custom key names by specifying config tag. Watches can be set on fields by using config tag aswell.

options (config.Options): can be used to set an additional configuration source (Consul or etcd) or custom configuration file path.

// import package
import ""

// define a struct
type myConfig struct {
    Kumuluz struct {
        Name    string
        Version string
        Env     struct {
            Name string
    } `config:"kumuluzee"`
    RestConfig struct {
        String  string `config:"string-property,watch"`
        Boolean bool   `config:"boolean-property"`
        Integer int    `config:"integer-property"`
    } `config:"rest-config"`

// make a struct instance & call config.NewBundle with a pointer to it
var myconf myConfig
config.NewBundle("", &myconf, config.Options{})



options (config.Options): can be used to set an additional configuration source (Consul or etcd) or custom configuration file path.

// import package
import ""

// usage
var confUtil config.Util

confUtil = config.NewUtil(config.Options{
    Extension: "consul",


Returns value of a given key. Returned value is of type interface{} and should be type asserted before further use. If key does not exist, returned value will be nil.

property := confUtil.Get("some-property")

There are additional helper functions available for getting a specific type:

value, ok := confUtil.GetBool(key) // bool
value, ok := confUtil.GetInt(key) // int
value, ok := confUtil.GetFloat(key) // float64
value, ok := confUtil.GetString(key) // string

Variable ok will evaluate to true if key exists and value is successfully type asserted.


Since configuration properties in Consul or etcd can be updated during microservice runtime, they have to be dynamically updated inside the running microservices. This behaviour can be enabled with watches.

If watch is enabled on a field, its value will be dynamically updated on any change in configuration source, as long as new value is of a proper type. For example, if value in configuration store is set to 'string' type and is changed to a non-string value, field value will not be updated.

While properties can be watched using config.Bundle by setting a watch tag on struct field, we can use config.Util to subscribe for changes using subscribe function.

confUtil.Subscribe(watchKey, func(key string, value string) {
    fmt.Printf("New value for key %s is %s\n", key, value)

Retry delays

Consul and etcd implementations support retry delays on watch connection errors. Since they use increasing exponential delay, two parameters need to be specified:

  • kumuluzee.config.start-retry-delay-ms, which sets the retry delay duration in ms on first error - default: 500
  • kumuluzee.config.max-retry-delay-ms, which sets the maximum delay duration in ms on consecutive errors - default: 900000 (15 min)


Recent changes can be viewed on Github on the Releases Page


See the contributing docs

When submitting an issue, please follow the guidelines.

When submitting a bugfix, write a test that exposes the bug and fails before applying your fix. Submit the test alongside the fix.

When submitting a new feature, add tests that cover the feature.