Add renku-search to deploy and check-pr action

check-pr-description/README.md

@@ -24,6 +24,7 @@ The supported components are:
 - `renku-ui` (that includes the `renku-ui-server` component, since the version is
   aligned between the 2 components)
 - `renku-data-services`
+- `renku-search`
 
 The reference will be stored in an output variable with the same name. For example,
 

check-pr-description/action.yaml

@@ -32,6 +32,9 @@ outputs:
   renku-data-services:
     description: renku-data-services reference as specified in the command string
     value: ${{ steps.check-string.outputs.renku-data-services }}
+  renku-search:
+    description: renku-search reference as specified in the command string
+    value: ${{ steps.check-string.outputs.renku-search }}
   amalthea:
     description: amalthea reference as specified in the command string
     value: ${{ steps.check-string.outputs.amalthea}}
@@ -96,6 +99,11 @@ runs:
               echo "renku-data-services reference: ${BASH_REMATCH[1]}"
               echo "renku-data-services=@${BASH_REMATCH[1]}" >> $GITHUB_OUTPUT
             fi
+            match="renku-search=(\S*)"
+            if [[ $command =~ $match ]]; then
+              echo "renku-search reference: ${BASH_REMATCH[1]}"
+              echo "renku-search=@${BASH_REMATCH[1]}" >> $GITHUB_OUTPUT
+            fi
             match="#notest"
             if [[ $command =~ $match ]]; then
               test_enabled=false

deploy-renku/README.md

@@ -41,6 +41,7 @@ deploy-pr:
       renku_notebooks: "${{ needs.check-deploy.outputs.renku-notebooks }}"
       renku_ui: "${{ needs.check-deploy.outputs.renku-ui }}"
       renku_data_services: "${{ needs.check-deploy.outputs.renku-data-services }}"
+      renku_search: "${{ needs.check-deploy.outputs.renku-search }}"
       extra_values: "${{ needs.check-deploy.outputs.extra-values }}"
 ```
 

deploy-renku/deploy-dev-renku.py

@@ -29,6 +29,7 @@
     "renku-notebooks",
     "renku-ui",
     "renku-data-services",
+    "renku-search",
     "amalthea",
 ]