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.

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

Variable extrapolation in configuration doesn't work in sub config. #6660

Closed
ph opened this issue Mar 26, 2018 · 1 comment
Closed

Variable extrapolation in configuration doesn't work in sub config. #6660

ph opened this issue Mar 26, 2018 · 1 comment

Comments

@ph
Copy link
Contributor

ph commented Mar 26, 2018

orignally reported in discuss at: https://discuss.elastic.co/t/environment-variables-not-replaced-in-external-configuration-file/124690

  • Version: 6.3.0 and 6.2.2
  • Operating System:
  • Steps to Reproduce:

Make theses changes to you YAML configuration

# filebeat.yml
custom.testing: ${CUSTOM_TESTING_ENV}
 filebeat.config.prospectors:
      enabled: true
     path: test.yml
# test.yml
- type: log
  enabled: true
  paths:
    - "/tmp/${custom.testing}"

Results into: Exiting: missing field accessing '0.paths.0'

Same problem if you using an environment variable directly in the sub configuration it won't get replaced.

@ph
Copy link
Contributor Author

ph commented Mar 26, 2018

When I've added the keystore #5737 in libbeat I've made some changes to the config handling, I will need to check if it got introduced by it or not.

@ph ph closed this as completed Aug 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant