TheHive-Project / TheHive-Project/Cortex
Allowing parameterization of ES username, password and Index through environment variables
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 264
- PR merge metrics
- No merged PRs in 30d
Description
Request Type
Feature Request
Work Environment
| Question | Answer |
|---|---|
| Cortex version / git hash | Latest |
| Package Type | Docker |
Problem Description
Currently, most of the relevant parameters for Cortex can be passed as environment variables. However, ES credentials need to be passed through configuration file which in a CI/CD pipeline may not be practical if we want to avoid custom containers.
It should also be possible to parameterize the index through environment variables so that the user can have a dev and prod env for Cortex. Otherwise, if i have two instances of Cortex, they will write to the same ES index.
Possible Solutions
Adjust Docker entrypoint code to allow the following variables:
- ES_USERNAME
- ES_PASSWORD
- ES_INDEX
Contributor guide
No contributing guide indexed for this repository
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
Locate the Docker entrypoint code and trace how Cortex configuration is populated from environment variables. Add support for ES_USERNAME, ES_PASSWORD, and ES_INDEX, then verify that separate Docker deployments can use distinct Elasticsearch credentials and indices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, elasticsearch
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100