search

neo4j-contrib / neo4j-helm

Helm Charts for running Neo4j on Kubernetes [DEPRECATED]
https://neo4j-contrib.github.io/neo4j-helm/user-guide/USER-GUIDE.html
Apache License 2.0
88 stars 81 forks source link

Unable to set apoc.trigger.enabled in neo4j.conf #211

Open ashwin-ginoria opened 3 years ago

ashwin-ginoria commented 3 years ago

Describe the bug values.yaml unable to set apoc.trigger.enabled in neo4j.conf neo4j version 4.3.2 helm version v3.6.3 chart version 4.3.2-1

To Reproduce Steps to reproduce the behavior:

  1. Run with values 
    
neo4j:
password: "my-password"
resources:
cpu: "2"

Neo4j configuration (yaml format)

config: apoc.trigger.enabled: "true" dbms.default_database: "neo4j" dbms.config.strict_validation: "true" dbms.connector.https.enabled: "true"


2. run `helm install mygraph  https://github.com/neo4j-contrib/neo4j-helm/releases/download/4.3.2-1/neo4j-4.3.2-1.tgz --set core.standalone=true --set acceptLicenseAgreement=yes --set neo4jPassword=mySecretPassword -f values.yml` 
3. Go to neo4j browser and run `CALL apoc.trigger.list()`

**Expected behavior**
Should return an empty list in neo4j browser.
rukaury commented 2 years ago

Try using environment variables:

remove the apoc config line in your yaml and add this at the end

env: { NEO4J_apoc_trigger_enabled: "true" }

It may also not work, i tried setting the apoc.import.file.enabled configuration using environment variables, i can see them in the neo4j.conf file when i exec into the pod, but neo4j browser says they are not enabled.