neo4j suitability spike artefacts added #42
Conversation
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
maniSbindra
force-pushed
the
manisbindra/add-neo4j-import-scripts-queries-dashboard
branch
from
df865d7 to
c75d544
Compare
| resources: | ||
| cpu: "0.5" | ||
| memory: "2Gi" | ||
| password: "INITIAL_DB_PASSWORD" # <-- Change this to your own password #gitleaks:allow |
Check warning
Code scanning / Gitleaks
hashicorp-tf-password has detected secret for file storage/neo4j/scripts/import/neo4j-helm-values.yaml at commit c75d5442be018ad1daf468a01127786aa9ce6ae4.
workaround to fix gitleaks false positive
maniSbindra
force-pushed
the
manisbindra/add-neo4j-import-scripts-queries-dashboard
branch
from
ad3747f to
c2e2847
Compare
Fixes #41
This PR contains artefacts created as a part of spike to investigate the suitability of using a graph database like Neo4j instead of Postgres (RDBMS) as the backend database of Kalypso Observability Hub.
The artefacts include: