OSB-59: load demo data to opensearch during initialization of package#75
OSB-59: load demo data to opensearch during initialization of package#75sniedzielski wants to merge 8 commits intodevelopfrom
Conversation
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 14324252 | Triggered | Generic Password | 049488d | .env.openSearch.example | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
|
|
|
||
| cd /openimis-be/openIMIS | ||
|
|
||
| exec python3 manage.py upload_opensearch_dashboards --host-domain http://backend:8080 --imis-password "${OPENIMIS_ADMIN_PASS}" |
There was a problem hiding this comment.
why port 8080 ? Also I thought that the pass was not mandatory anymore,:
why not pushing it directly to openSearch, you have OS credentials available
2 participants
TICKET: https://openimis.atlassian.net/browse/OSB-59
PR introduces additional 'intermediate' container responsible for loading opensearch demo settings/examples.