Do not override solr-update-core-and-start in the compose and stack files

The ghcr.io/kitconcept/solr image sets CMD
["solr-update-core-and-start"], which refreshes the config of an already
existing core before calling solr-precreate. All three places that start
Solr then set a command: of their own with plain solr-precreate, which
replaces the CMD and disables the refresh, so a core that already exists
on a volume keeps its old config.

Call the script explicitly instead of relying on the CMD, so adding a
command: back later cannot silently switch it off again.

Author: reekitconcept

devops/stacks/demo.yml

@@ -99,9 +99,7 @@ services:
   solr:
     image: ghcr.io/kitconcept/solr:${SOLR_TAG:-feature-ai-rag}
     command:
-      - solr-precreate
-      - plone
-      - /plone-config
+      - solr-update-core-and-start
     environment:
       SOLR_MODULES: extraction
       SOLR_OPTS: "-Dsolr.tika.url=http://${STACK_NAME}-tika:9998"

devops/stacks/persistent.yml

@@ -134,9 +134,7 @@ services:
   solr:
     image: ghcr.io/kitconcept/solr:${SOLR_TAG:-feature-ai-rag}
     command:
-      - solr-precreate
-      - plone
-      - /plone-config
+      - solr-update-core-and-start
     environment:
       SOLR_MODULES: extraction
       SOLR_OPTS: "-Dsolr.tika.url=http://${STACK_NAME}-tika:9998"

docker-compose-dev.yml

@@ -57,9 +57,7 @@ x-solr: &solr
   ports:
     - 8983:8983
   command:
-    - solr-precreate
-    - plone
-    - /plone-config
+    - solr-update-core-and-start
   environment:
     SOLR_MODULES: extraction
 

news/+solr-update-core-not-overridden.internal

@@ -0,0 +1 @@
+Stop overriding the Solr image `CMD` with `solr-precreate`, so config updates reach an existing core (kitconcept/kitconcept.solr#107). @reekitconcept