feat: add graph data science (gds) plugin to neo4j deployment#55
Merged
Conversation
Add GDS Community 2.13.8 alongside existing APOC 5.26.22 to match the production configuration now deployed across both primary and secondary hosts. GDS enables graph algorithms for analysis and pattern detection. Changes: - docker-compose.yml: Add 'graph-data-science' to NEO4J_PLUGINS and extend security.procedures.unrestricted to cover gds.* in addition to apoc.* - neo4j.Dockerfile: Add build-time download of GDS Community 2.13.8 jar, pinned to the official Neo4j 5.26.x compatibility matrix - docs/service-setup.md: Update Docker Compose and docker run quickstarts to show APOC+GDS as default configuration; document air-gap behavior for GDS (network needed at container start for non-baked, at build-time for baked) - test/airgap/verify-airgap-apoc.sh: Extend air-gap regression test to verify GDS jar is baked into the image layer alongside APOC; add GDS_VERSION env override Verification: Full air-gap test suite pass, including new GDS baked-jar check, confirmed GDS procedures callable on fully internal Docker network, and docker compose config validation successful on both compose YAML files. No data loss or connectivity interruption on either production host during in-place container rebuild. 🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier) Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
colombod
approved these changes
Jul 11, 2026
colombod
added a commit
that referenced
this pull request
Jul 11, 2026
Surface the real fixes from PR #55 (feat: add graph data science plugin): - Drop the wrong `dbms.security.procedures.allowlist=apoc.*,gds.*` from the bare-metal Neo4j VM config in azure-deployment.md — an allowlist restricted to the plugins would block the built-in db.*/dbms.* procedures the server needs. Set ONLY `unrestricted`. - local-development.md docker run: add explicit `NEO4J_dbms_security_procedures_unrestricted='apoc.*,gds.*'` so GDS procedures load, pin the image to neo4j:5.26.22-community, and document that GDS is fetched at first start matched to the Neo4j version per the official compatibility matrix (GDS 2.13.x for Neo4j 5.26.x). 🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier) Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
colombod
added a commit
that referenced
this pull request
Jul 11, 2026
Surface the real fixes from PR #55 (feat: add graph data science plugin): - Drop the wrong `dbms.security.procedures.allowlist=apoc.*,gds.*` from the bare-metal Neo4j VM config in azure-deployment.md — an allowlist restricted to the plugins would block the built-in db.*/dbms.* procedures the server needs. Set ONLY `unrestricted`. - local-development.md docker run: add explicit `NEO4J_dbms_security_procedures_unrestricted='apoc.*,gds.*'` so GDS procedures load, pin the image to neo4j:5.26.22-community, and document that GDS is fetched at first start matched to the Neo4j version per the official compatibility matrix (GDS 2.13.x for Neo4j 5.26.x). 🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier) Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
colombod
added a commit
that referenced
this pull request
Jul 13, 2026
Surface the real fixes from PR #55 (feat: add graph data science plugin): - Drop the wrong `dbms.security.procedures.allowlist=apoc.*,gds.*` from the bare-metal Neo4j VM config in azure-deployment.md — an allowlist restricted to the plugins would block the built-in db.*/dbms.* procedures the server needs. Set ONLY `unrestricted`. - local-development.md docker run: add explicit `NEO4J_dbms_security_procedures_unrestricted='apoc.*,gds.*'` so GDS procedures load, pin the image to neo4j:5.26.22-community, and document that GDS is fetched at first start matched to the Neo4j version per the official compatibility matrix (GDS 2.13.x for Neo4j 5.26.x). 🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier) Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add GDS Community 2.13.8 alongside existing APOC to match production configuration now deployed across both primary and secondary hosts. This brings the repository in line with actual deployed infrastructure — no configuration drift between repo definitions and running containers.
GDS (Graph Data Science) Community enables graph algorithms for analysis and pattern detection on Neo4j. The plugin versions are pinned to Neo4j's official compatibility matrix (GDS 2.13.8 with Neo4j 5.26.x).
What changed
Test plan
🤖 Generated with Amplifier