ROX-30064: Script to generate catalog-template.yaml

.gitignore

@@ -3,3 +3,6 @@
 
 # Leftover staging directory for importing legacy catalog. Can be safely deleted
 /catalog-migrate/
+
+# Ignore VS code local settings
+.vscode

.tekton/check-generated-files-up-to-date-task.yaml

@@ -27,17 +27,15 @@ spec:
     - use
     - $(params.SOURCE_ARTIFACT)=/var/workdir/source
   - name: check-generated-files-up-to-date
-    image: registry.access.redhat.com/ubi9:latest@sha256:d4feb579a84ead49894ec71fe54f14300992e202f3491d9bb22b62cc57affd49
+    image: registry.redhat.io/ubi9/go-toolset@sha256:2e8adc5be8eba060e919a6f7309a7b5ef09dd72d3ae9e747b9eb02e96f35a0f5
     workingDir: /var/workdir/source
+    securityContext:
+      runAsUser: 0
     script: |
       #!/usr/bin/env bash
       set -euo pipefail
       set -x
 
-      time dnf -y upgrade --nobest
-      # TODO: find an image with these preinstalled to reduce flakiness
-      time dnf -y install git make jq
-
       time make clean
       cmd="make valid-catalogs"
       time $cmd

.tekton/checks.yaml

@@ -85,6 +85,28 @@ spec:
       - name: basic-auth
         workspace: git-auth
 
+    - name: run-go-unit-tests
+      taskSpec:
+        metadata:
+          name: run-go-unit-tests
+        volumes:
+        - name: workdir
+          emptyDir: { }
+        stepTemplate:
+          volumeMounts:
+          - mountPath: /var/workdir
+            name: workdir
+        steps:
+        - name: use-trusted-artifact
+          image: quay.io/redhat-appstudio/build-trusted-artifacts:latest@sha256:9b180776a41d9a22a1c51539f1647c60defbbd55b44bbebdd4130e33512d8b0d
+          args:
+          - use
+          - $(tasks.clone-repository.results.SOURCE_ARTIFACT)=/var/workdir/source
+        - name: run-go-tests
+          image: registry.redhat.io/ubi9/go-toolset@sha256:3ce6311380d5180599a3016031a9112542d43715244816d1d0eabc937952667b
+          workingDir: /var/workdir/source
+          script: time make go-test
+
     - name: check-generated-files-up-to-date
       params:
       - name: SOURCE_ARTIFACT

Makefile

@@ -6,13 +6,18 @@ MAKEFLAGS += "-j 2"
 
 OPM = .bin/opm-$(OPM_VERSION)
 
+GO := go
+
+GENERATE_SCRIPT_FOLDER = ./cmd/generate-catalog/
+
 .PHONY: valid-catalogs
 valid-catalogs: $(CATALOGS) $(OPM)
 	$(OPM) validate catalog-bundle-object
 	$(OPM) validate catalog-csv-metadata
 
 .PHONY: clean
 clean:
+	rm -f catalog-template.yaml
 	rm -f $(CATALOGS)
 	rm -rf $$(dirname $(OPM))
 
@@ -24,6 +29,13 @@ catalog-csv-metadata/rhacs-operator/catalog.json: catalog-template.yaml $(OPM)
 	mkdir -p "$$(dirname "$@")"
 	$(OPM) alpha render-template basic --migrate-level bundle-object-to-csv-metadata $< > $@
 
+# update template/catalog-template.yaml based on bundles.yaml file.
+catalog-template.yaml: bundles.yaml $(wildcard $(GENERATE_SCRIPT_FOLDER)/*.go)
+	@$(GO) run $(GENERATE_SCRIPT_FOLDER)
+
+go-test:
+	@$(GO) test -cover -v ./cmd/...
+
 $(OPM):
 	mkdir -p "$$(dirname $@)"
 	os_name="$$(uname | tr '[:upper:]' '[:lower:]')"; \

README.md

@@ -9,96 +9,30 @@ OperatorHub.
 ### Restarting Konflux pipeline
 
 If some pipeline failed, you can restart it by commenting in the PR `/test <pipeline-name>` (e.g. `/test operator-index-ocp-v4-16-on-push`).
-See more in [our docs](https://spaces.redhat.com/display/StackRox/How+to+everything+Konflux+for+RHACS#HowtoeverythingKonfluxforRHACS-Howtore-runpipelines).
+See more in [our docs](https://spaces.redhat.com/spaces/StackRox/pages/702155579/How+to+re-run+Konflux+pipelines).
 
 ### <a name="add-bundle"></a> Adding new ACS operator version
 
-Do the following changes in the `catalog-template.yaml` file.
-
-1. Add bundle image.
-   1. Find entries with `schema: olm.bundle` towards the end of the file.
-   2. Add a new entry for your bundle image.\
-      It should look something like this:
-      ```yaml
-      - schema: olm.bundle
-        # 4.7.9
-        image: quay.io/rhacs-eng/release-operator-bundle@sha256:c82e8330c257e56eb43cb5fa7b0c842a7f7f0414e32e26a792ef36817cb5ca02
-      ```
-      * Note that the image must be referenced by digest, not by tag.
-      * Keep entries sorted according to version.
-      * Add a comment stating the version, see how it's done for other items there.
-      * You may add bundle images from `quay.io`, `brew.registry.redhat.io` and so on (provided they exist and are
-        pullable) during development and/or when preparing to release.\
-        Ultimately, all released bundle images must come from
-        `registry.redhat.io/advanced-cluster-security/rhacs-operator-bundle` repo because this is where customers expect
-        to find them. There's a CI check which prevents pushing to `master` if there's any bundle from
-        a different repo.
-2. Add entry to the `stable` channel.
-   1. Find the `stable` channel block. It starts with:
-      ```yaml
-      - schema: olm.channel
-        name: stable
-      ```
-   2. Add a new item into its `entries` list.
-      * Entries must be sorted by version (e.g., you must insert `4.8.2` after `4.8.1` but before `4.9.0`).
-      * Ensure there are consistent blank lines between entries of different Y-streams.
-      * Entry format is
-        ```yaml
-        - &bundle-4-Y-Z
-          name: rhacs-operator.v4.Y.Z
-          replaces: rhacs-operator.v4.PREVIOUS_Y.PREVIOUS_Z
-          skipRange: '>= 4.(Y-1).0 < 4.Y.Z'
-        ```
-        Replace
-        * `Y` with minor version (e.g., `8` in `4.8.2`),
-        * `Z` with patch version (e.g., `2` in `4.8.2`),
-        * `PREVIOUS_Y` and `PREVIOUS_Z` with minor and patch versions of the previous item (e.g., when you add `4.8.2`
-          after `4.8.1`, that'd be `8` and `1`; when you add `4.9.0` after `4.8.3`, that'd be `8` and `3`),
-        * `(Y-1)` with the value of `Y` minus 1 (e.g., when you add `4.8.2`, that'd be `7`).
-   3. If the item you added is not the last one in the `entries` list, i.e., not the highest version, adjust the next
-      item in the `entries` list.\
-      Set its `replaces:` to be `rhacs-operator.v4.Y.Z`.\
-      For example:
-      ```yaml
-      - &bundle-4-7-4  # <-------- this was already there
-        name: rhacs-operator.v4.7.4
-        replaces: rhacs-operator.v4.7.3
-        skipRange: '>= 4.6.0 < 4.7.4'
-      - &bundle-4-7-5  # <-------- this one I'm adding
-        name: rhacs-operator.v4.7.5
-        replaces: rhacs-operator.v4.7.4
-        skipRange: '>= 4.6.0 < 4.7.5'
-
-      - &bundle-4-8-0  # <-------- this was already there
-        name: rhacs-operator.v4.8.0
-        replaces: rhacs-operator.v4.7.4   # <-------- must change here to rhacs-operator.v4.7.5
-        skipRange: '>= 4.7.0 < 4.8.0'
-      ```
-3. Add entry to `rhacs-4.?` channels.
-   * For every `schema: olm.channel` with `name` like `rhacs-4.?` where `?` is >= `Y`,
-   * add `- *bundle-4-Y-Z` to the `entries:` list (replacing `Y` and `Z` with minor and patch versions).
-   * Maintain the entries sorted and with consistent linebreaks.
-4. Add `rhacs-4.Y` channel. Skip this step if the channel already exists (i.e., when `Z` > `0`).
-   * Keep the channels sorted.
-   * In the `entries:`, reference all items from `4.0.0` up to (and including) `4.Y.Z`.
-
-   It should look something like this (replacing `Y`, `Z` as appropriate):
+1. Open `bundles.yaml` file.
+2. Add a new operator bundle image with version. It would look like this:
    ```yaml
-   - schema: olm.channel
-     name: rhacs-4.Y
-     package: rhacs-operator
-     entries:
-     - *bundle-4-0-0
-     - *bundle-4-0-1
-     # ... and so on ...
-
-     - *bundle-4-Y-Z
+      - image: quay.io/rhacs-eng/release-operator-bundle@sha256:c82e8330c257e56eb43cb5fa7b0c842a7f7f0414e32e26a792ef36817cb5ca02
+        version: 4.7.9
    ```
+   * Note that the image must be referenced by digest, not by tag.
+   * Keep entries sorted by version.
+   * You may add bundle images from `quay.io`, `brew.registry.redhat.io` and so on (provided they exist and are pullable) during development and/or when preparing to release.  
+      Ultimately, all released bundle images must come from
+      `registry.redhat.io/advanced-cluster-security/rhacs-operator-bundle` repo because this is where customers expect
+      to find them. There's a CI check which should make it impossible to push to `master` if there's any bundle from
+      a different repo.
+3. Update `oldest_supported_version` value:
+   * Check `Life Cycle Dates` table in [Red Hat Advanced Cluster Security for Kubernetes Support Policy](https://access.redhat.com/support/policy/updates/rhacs).
+   * Set `oldest_supported_version` to be the oldest Y-Stream version still in support according to that table, including Maintenance Support. Patch number should always be `.0`. For example, if 4.6 is the oldest in support (maintenance phase), set `oldest_supported_version: 4.6.0`.
+4. Update catalogs (follow [updating catalogs steps](#updating-catalogs))
+5. Open a PR with `Add 4.Y.Z version` title.
 
-Once done with `catalog-template.yaml`:
 
-1. Update catalogs (follow [updating catalogs](#updating-catalogs) steps below).
-2. Open a PR with `Add 4.Y.Z version` title.
 
 ### Updating catalogs
 
@@ -108,7 +42,7 @@ make clean && make valid-catalogs
 ```
 Note: this will take a while.
 
-If a new bundle was added then you should see that `catalog-bundle-object/rhacs-operator/catalog.json` and `catalog-csv-metadata/rhacs-operator/catalog.json` files are changed.
+If a new bundle was added then you should see that `catalog-template.yaml`, `catalog-bundle-object/rhacs-operator/catalog.json` and `catalog-csv-metadata/rhacs-operator/catalog.json` files are changed.
 
 #### Historical note