Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cherry-pick #20898 to 7.x: Avoid generating incomplete configurations in autodiscover #20919

Merged
merged 2 commits into from
Sep 3, 2020
Merged

Cherry-pick #20898 to 7.x: Avoid generating incomplete configurations in autodiscover #20919

merged 2 commits into from
Sep 3, 2020

Commits on Sep 2, 2020

  1. Avoid generating incomplete configurations in autodiscover (elastic#2… 

    …0898)

Handle errors when configuration unpacking fails. In principle this can
only happen when some variable is missing, because configuration has
been previously parsed as YAML. Errors on unpacking were previously
ignored.

When a variable is missing, this is clearly logged at the debug level.

This changes the behaviour, previously an incomplete configuration was
generated on this case.

(cherry picked from commit 99fd545)
    @jsoriano
    jsoriano committed Sep 2, 2020
    Configuration menu
    Copy the full SHA
    74cd90b View commit details
    Browse the repository at this point in the history

  2. Fix changelog

    @jsoriano
    jsoriano committed Sep 2, 2020
    Configuration menu
    Copy the full SHA
    7a44125 View commit details
    Browse the repository at this point in the history