opensearch-project / opensearch-project/data-prepper
Use environment variables in data prepper configs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
Other logforwarders support the use of environment variables in configs. Logstash and FLuentbit both support the ${ENV_VAR} notation in their config files. This is useful in docker/kubernetes implementations where you might have several instances using the same config data. The data prepper docs don't reference this so I presume it's not supported yet.
Describe the solution you'd like
Use environment variables in the configs like Fluent-bit and Logstash do
Describe alternatives you've considered (Optional)
None
Additional context
None
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files, tests, or configuration entry points; start by reviewing the comment thread and locating how Data Prepper reads its configs. Done means the intended ${ENV_VAR} behavior is supported consistently and documented for Docker/Kubernetes deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100