Skip to content

Settings: Fix settings reading to account for defaults#22871

Merged
rjernst merged 1 commit intoelastic:masterfrom
rjernst:fix_default_props
Jan 30, 2017
Merged

Settings: Fix settings reading to account for defaults#22871
rjernst merged 1 commit intoelastic:masterfrom
rjernst:fix_default_props

Conversation

@rjernst
Copy link
Copy Markdown
Member

@rjernst rjernst commented Jan 30, 2017

In #22762, settings preparation during bootstrap was changed slightly to
account for SecureSettings, by starting with a fresh settings builder
after reading the initial configuration. However, this the defaults from
system properties were never re-read. This change fixes that bug (which
was never released).

closes #22861

In elastic#22762, settings preparation during bootstrap was changed slightly to
account for SecureSettings, by starting with a fresh settings builder
after reading the initial configuration. However, this the defaults from
system properties were never re-read. This change fixes that bug (which
was never released).

closes elastic#22861
@rjernst
Copy link
Copy Markdown
Member Author

rjernst commented Jan 30, 2017

I've marked this as a non-issue because no release was ever done with the bug. @clintongormley Is there a better way to avoid this showing up in release notes?

@rjernst
Copy link
Copy Markdown
Member Author

rjernst commented Jan 30, 2017

I'm going to push this to fix the failing packaging tests. I will be happy to do any followups if there are concerns.

@rjernst rjernst merged commit a4f6ede into elastic:master Jan 30, 2017
@rjernst rjernst deleted the fix_default_props branch January 30, 2017 22:42
rjernst added a commit that referenced this pull request Jan 30, 2017
In #22762, settings preparation during bootstrap was changed slightly to
account for SecureSettings, by starting with a fresh settings builder
after reading the initial configuration. However, this the defaults from
system properties were never re-read. This change fixes that bug (which
was never released).

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Wrong config directory is picked up

1 participant