Skip to content

Commit 634b03a

Browse files
authored
Update in note for setting env varibales rules
1 parent cd694c9 commit 634b03a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/send-data/opentelemetry-collector/remote-management/st-with-secrets.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@ Below are the steps to make things work for such source templates:
2020
1. Set env variable in OpenTelemetry Collector process. For example: `SECRET_ENV_VAR=Welcome@123`, where `SECRET_ENV_VAR` is the variable name and `Welcome@123` is the password.
2121
2. ST creation: While creating the source template you will need to provide the environment variable name instead of the actual password. In this case: `SECRET_ENV_VAR` and this will be part of the source template referring to the value of the environment variable like: `password: ${env:SECRET_ENV_VAR}`.
2222
3. Once this source template gets pushed to the respective OpenTelemetry collector, the environment variable will get resolved at runtime and will be substituted with the actual password value to make the config work and pull the data to send it to Sumo Logic.
23-
^[a-zA-Z_][a-zA-Z0-9_]*$
23+
2424
:::note
25-
Environment variable can start with small or capital character or an underscore(_) followed by any letters(small or capital), numbers and underscore.
25+
Environment variable should start with small or capital character or an underscore(_) followed by any letters(small or capital), numbers and underscore.
2626
:::
2727

2828
This way, your secret data is not shared with Sumo Logic.

0 commit comments

Comments
 (0)