Conversation
…alues of ${ENV} (#16365)
* Properly resolve the values from ENV vars if literal array string provided with ENV var.
* Docker acceptance test for persisting keys and use actual values in docker container.
* Review suggestion.
Simplify the code by stripping whitespace before `gsub`, no need to check comma and split.
Co-authored-by: João Duarte <jsvd@users.noreply.github.com>
---------
Co-authored-by: João Duarte <jsvd@users.noreply.github.com>
(cherry picked from commit 62ef8a0)
|
💚 Build Succeeded
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.





Backport PR #16365 to 8.15 branch, original message:
Release notes
A bug (introduced in 8.13.1) fix to use array value with docker environment variables (such as
XPACK_MANAGEMENT_PIPELINE_ID,XPACK_MANAGEMENT_ELASTICSEARCH_HOSTS).What does this PR do?
Fixes the bug introduced by #16026. After 8.13.1, running Logstash on docker with list environment variable (example:
-e XPACK_MANAGEMENT_ELASTICSEARCH_HOSTS='[es.host.1, es.host.2:9500]') doesn't work. Current change fixes this issue.Why is it important/What is the impact to the user?
Checklist
Author's Checklist
How to test this PR locally
run
rake artifact:dockerto build docker imageuse the hash value created by rake and replace
b6c644b81357d29d9ae30b788fad327ece26d363c3541e566c543dc9dc084874with your hash valueENV var carries list:
Related issues
Use cases
Screenshots
Logs