docs: Fix documentation about using environment variables to obfuscate sensitive values #18432
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.
Please follow conventional commit standards
in your commit messages and pull request title.
Give us some context
Adds missing whitespaces between the curly brackets and the environment variable name. Without them, these are interpreted literally.
In the tests that fixed an issue with variable passthrough, they do have whitespaces https://github.com/newrelic/nri-kubernetes/blob/main/charts/newrelic-infrastructure/tests/configmap_integrations_test.yaml#L231
We spent quite some time trying to figure out why the variables were not working, only to find out it was due to the whitespaces 😅