Skip to content
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.

Specify a specific version of plugin to install #225

Open
brunocous opened this issue Oct 25, 2021 · 1 comment
Open

Specify a specific version of plugin to install #225

brunocous opened this issue Oct 25, 2021 · 1 comment

Comments

@brunocous
Copy link

brunocous commented Oct 25, 2021

According to the configuration documentation, the list of specifiable plugins can be found in https://github.com/neo4j/docker-neo4j/blob/master/neo4jlabs-plugins.json.
Digging deeper, it defines a mapping from neo4j version to specific plugin version.

My questions are:

  • Is there a reason why specific version of Neo4j should be pinned to a specific version of a plugin?
  • What I would like to control which plugin version will be installed, what is the best way forward to do this cleanly without manual installation?
@brunocous
Copy link
Author

I have found the following piece of code in the values.yaml. Will try it now.

initContainers: []
  ## init containers to run before the Neo4j replica pod e.g. to install custom plugins
  ## They can also be used to restore from last available backup, to ensure that newly joining
  ## core members have less TX history to catch up on before joining the cluster.
  ## Note that this is specifically *not* needed for APOC, which is included by default.
  # - name: init-plugins
  #   image: "appropriate/curl:latest"
  #   imagePullPolicy: "IfNotPresent"
  #   volumeMounts:
  #   - name: plugins
  #     mountPath: /plugins
  #   command:
  #     - "/bin/sh"
  #     - "-c"
  #     - |
  #       curl -L https://somesite.com/path/to/plugin.jar -O
  #       cp plugin.jar /plugins/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant