Skip to content

Commit

Permalink
Add changelog for 0.14.2 (m3db#2014)
Browse files Browse the repository at this point in the history
  • Loading branch information
robskillington authored Oct 25, 2019
1 parent de7f9ea commit 4e589d5
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 16 deletions.
15 changes: 10 additions & 5 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,16 @@
# Changelog

# 0.14.2 (upcoming)
# 0.14.2

## Features
- **Config**: support env var expansion using go.uber.org/config.
- **Config**: Deprecate listenaddress expansion in favor of go.uber.org/config
env var expansion ([#2017](https://github.com/m3db/m3/pull/2017/files))
## Bug Fixes

- **M3DB**: Fix the persist cycle not cleaning up state for reuse when flush times cannot be calculated ([#2007](https://github.com/m3db/m3/pull/2007))

## Misc

- **M3Aggregator**: Do not require aggregator ID to be joined with port and add instance initialization debug logs ([#2012](https://github.com/m3db/m3/pull/2012))
- **All**: Support env var expansion using [go.uber.org/config](go.uber.org/config) ([#2016](https://github.com/m3db/m3/pull/2016))
- **All**: Deprecate listen address expansion in favor of [go.uber.org/config](go.uber.org/config) env var expansion ([#2017](https://github.com/m3db/m3/pull/2017))

# 0.14.1

Expand Down
15 changes: 4 additions & 11 deletions config/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,17 +40,12 @@ std.manifestYamlDoc(lib(cluster, coordinator))

## Configuration Schemas

At this time, each service's configuration is defined as a Go struct in a
corresponding `config` package. For instance, `m3aggregator`'s config is
in [src/cmd/services/m3aggregator/config/config.go](https://github.com/m3db/m3/blob/master/src/cmd/services/m3aggregator/config/config.go).
At this time, each service's configuration is defined as a Go struct in a corresponding `config` package. For instance, `m3aggregator`'s config is in [src/cmd/services/m3aggregator/config/config.go](https://github.com/m3db/m3/blob/master/src/cmd/services/m3aggregator/config/config.go).

Validation is done using https://godoc.org/gopkg.in/go-playground/validator.v2 ;
look for `validate` tags.
Validation is done using [https://godoc.org/gopkg.in/go-playground/validator.v2](https://godoc.org/gopkg.in/go-playground/validator.v2), look for `validate` tags in the structs.

## Advanced: Environment Variable Interpolation
M3 uses [go.uber.org/config](https://godoc.org/go.uber.org/config) to load
its configuration. This means that we support environment variable interpolation
of configs. For example:
M3 uses [go.uber.org/config](https://godoc.org/go.uber.org/config) to load its configuration. This means that we support environment variable interpolation of configs. For example:

Given the following config:

Expand All @@ -63,7 +58,5 @@ and an environment of `MY_ENV_VAR=bar`, the interpolated YAML will be:
```
foo: bar
```
.

This can be useful for further tweaking your configuration without generating
different files for every config permutation.
This can be useful for further tweaking your configuration without generating different files for every config permutation.

0 comments on commit 4e589d5

Please sign in to comment.