Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a script to *AUTOMATICALLY* update APOC.core/APOC.extended jars to match the version of Neo4j server currently installed. #713

Closed
numericOverflow opened this issue Jan 6, 2025 · 1 comment

Comments

@numericOverflow
Copy link

Guidelines

Feature description (Mandatory)

Some way (python, shell, ect. script) to automatically update my APOC.core & APOC.extended jars to match the version of Neo4j server installed.

It doesn't have to be fully automatic (ie lights-out, no interaction), but at least automatable (ie I can schedule or keep everything in sync when one is updated).

Considered alternatives

Right now Neo4j-Sever can be automated, but APOC.core & APOC.extended as completely done MANUALLY. This leads to all sorts of pain and trouble because in our DEV environment the server is auto-updated by the system (RHEL "dnf" package manager) so I don't always know when an update has occurred. They (APOC.* and Neo4j-Sever) are frequently out-of-sync

How this feature can improve the project?

Reduce headaches for admins. Right now it's a manual, disjointed process but requires versions be exactly paired. The distribution of the Neo4j server and the associated APOC.core & APOC.extended are completely independent. This leads to a TON of babysitting, troubleshooting, and gnashing of teeth when they are out of sync (which happens quite often).

@JoelBergstrand
Copy link
Contributor

Hello @numericOverflow, APOC Core is currently in maintenance mode and does not accept feature requests currently. If you would like to have your request considered please submit your request to the APOC extended repo instead.

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

No branches or pull requests

2 participants