Skip to content

feat: Allow overriding history file through env variable#96

Merged
as51340 merged 2 commits intomasterfrom
feat/new-history-file
Apr 22, 2026
Merged

feat: Allow overriding history file through env variable#96
as51340 merged 2 commits intomasterfrom
feat/new-history-file

Conversation

@as51340
Copy link
Copy Markdown
Contributor

@as51340 as51340 commented Apr 22, 2026

Allow overriding of the history file through env variables.

@as51340 as51340 force-pushed the feat/new-history-file branch from 3086c3f to 9283dee Compare April 22, 2026 11:23
Copy link
Copy Markdown
Contributor

@mattkjames7 mattkjames7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@as51340 as51340 changed the title feat: Define new default value for --history flag feat: Allow overriding history file through env variable Apr 22, 2026
@as51340 as51340 merged commit 36af360 into master Apr 22, 2026
8 checks passed
as51340 added a commit to memgraph/helm-charts that referenced this pull request May 4, 2026
Read-only root filesystem change is connected to memgraph/mgconsole#96 because mgconsole uses a history file by default from /home/memgraph/.memgraph. Now, we will use env variable MGCONSOLE_HISTORY_PATH.

The env section is removed because the new default way of setting license key and organisation name will be through secrets. Secrets will not support anymore setting user through env variables, users should manually create users by running Cypher queries on data instances. The current design was not clean enough because env variables were also applied to coordinators which didn't make any sense since coordinators are running without auth.

Fixed the bug when boolean value is passed as label value with nodeSelection enabled.
Fixed the bug with namespace usage in vmagent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants