New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

defaults overriding file settings #14

Closed
gnomff opened this Issue Aug 6, 2015 · 5 comments

Comments

Projects
None yet
2 participants
@gnomff

gnomff commented Aug 6, 2015

When I set a default value in defaults.yaml it is overriding the value set in the file config. Example:

defaults.yaml

global:  
  myval: 'default_value'  

common.yaml

data_sources:
  - defaults
  - file
  - environment_json
  - environment

template_sources:
  - file

production.yaml

myproperties.properties.erb:
  target: /my/path/myproperties.properties
  config:
    myval: 'override_value'

when I run tiller I get:
Warning, merging duplicate global and local values.
myval => 'override_value' being replaced by : 'default_value' from merged configuration

I am using v0.6.0

@markround

This comment has been minimized.

Owner

markround commented Aug 7, 2015

Thanks for the report, I'll check this out...

@markround

This comment has been minimized.

Owner

markround commented Aug 7, 2015

Hi!

I've made a quick fix (a8f8d83). Can you try upgrading to 0.6.4 and then replace your tiller binary with this one : https://raw.githubusercontent.com/markround/tiller/feature/defaults_bugfix/bin/tiller and see if it works for you in your environment ?

Thanks,

-Mark

@gnomff

This comment has been minimized.

gnomff commented Aug 7, 2015

That seems to have done the trick. Thanks!

@markround

This comment has been minimized.

Owner

markround commented Aug 7, 2015

Great! Thanks again for the bug report, I'll merge this properly and release an updated 0.6.5 first thing next week.

@markround

This comment has been minimized.

Owner

markround commented Aug 10, 2015

@gnomff gnomff closed this Aug 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment