test,CI: pass experimental options to systemd unit when deploying

In the deploy script, after installing all the test RPMs, add an
override to the unit file that sets the IMAGE_BUILDER_EXPERIMENTAL
environment variable for the osbuild-composer service with any values
from the global runner environment.

If image-builder-manifest-generation is enabled, install image-builder
from the repos.

Add a single API test job (api.sh) to the gitlab CI config that uses the
new experimental job type.

In the api.sh script, when image-builder-manifest-generation is enabled
in the test, verify it was actually used by searching for the warning
that's logged when the job is enqueued.

Author: achilleas-k

.gitlab-ci.yml

@@ -605,6 +605,13 @@ API:
           - aws/rhel-10.0-ga-aarch64
         INTERNAL_NETWORK: ["true"]
 
+      # single test config for experimental feature
+      - IMAGE_TYPE: ["aws"]
+        RUNNER:
+          - aws/rhel-10.1-nightly-x86_64
+        IMAGE_BUILDER_EXPERIMENTAL: "image-builder-manifest-generation=1"
+        INTERNAL_NETWORK: ["true"]
+
 API-module-hotfixes:
   stage: test
   extends: .terraform

schutzbot/deploy.sh

@@ -136,6 +136,28 @@ retry sudo dnf -y install osbuild-tools
 # Save osbuild-composer NVR to a file to be used as CI artifact
 rpm -q osbuild-composer > COMPOSER_NVR
 
+IMAGE_BUILDER_EXPERIMENTAL="${IMAGE_BUILDER_EXPERIMENTAL:-}"
+if [[ "${IMAGE_BUILDER_EXPERIMENTAL}" != "" ]]; then
+    greenprint "Adding experimental options to osbuild-composer.service"
+    # Pass any experimental options into the systemd unit
+    cat > experimental-override.conf << EOF
+[Service]
+Environment=IMAGE_BUILDER_EXPERIMENTAL="${IMAGE_BUILDER_EXPERIMENTAL}"
+EOF
+
+    cat experimental-override.conf | sudo systemctl edit --stdin osbuild-composer.service
+    sudo systemctl daemon-reload
+    sudo systemctl cat osbuild-composer.service
+
+    if echo "${IMAGE_BUILDER_EXPERIMENTAL}" | grep -q "image-builder-manifest-generation=1"; then
+        # TODO: configure dependency pinning for image-builder like we do for osbuild
+        # https://issues.redhat.com/browse/HMS-9647
+        greenprint "Installing image-builder for experimental manifest generation"
+        sudo dnf -y install image-builder
+    fi
+fi
+
+
 if [ "${NIGHTLY:=false}" == "true" ]; then
     # check if we've installed the osbuild-composer RPM from the nightly tree
     # under test or happen to install a newer version from one of the S3 repositories

test/cases/api.sh

@@ -903,5 +903,14 @@ TOKEN="$(curl --request POST \
 sudo systemctl restart osbuild-remote-worker@localhost:8700.service
 sudo systemctl is-active --quiet osbuild-remote-worker@localhost:8700.service
 
+IMAGE_BUILDER_EXPERIMENTAL="${IMAGE_BUILDER_EXPERIMENTAL:-}"
+if [[ "${IMAGE_BUILDER_EXPERIMENTAL}" != "" ]]; then
+    if echo "${IMAGE_BUILDER_EXPERIMENTAL}" | grep -q "image-builder-manifest-generation=1"; then
+        greenprint "Verifying usage of experimental job type"
+        # verify using log message
+        journalctl -g "using experimental job type: image-builder-manifest"
+    fi
+fi
+
 greenprint  "DONE"
 exit 0