Skip to content

Conversation

@hardys
Copy link
Contributor

@hardys hardys commented Jan 8, 2026

Adds a script/template which allows us to generate the versions derived from the release manifest, hopefully this will be less effort and less error-prone than manual updates

Note this is a first step which requires running the script manually - in future we can add a check job to enforce its use, and potentially look at ways to automate the updates via a renovate type flow.

Adds a script/template which allows us to generate the versions
derived from the release manifest, hopefully this will be less
effort and less error-prone than manual updates
Copy link
Contributor

@diconico07 diconico07 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly usability comments. This will be a really nice addition 👍

RELEASE_BRANCH=${RELEASE_BRANCH_:-"main"}

echo "Downloading release manifest for ${RELEASE_BRANCH} branch"
curl "https://src.opensuse.org/suse-edge/Factory/raw/branch/${RELEASE_BRANCH}/release-manifest-image/release_manifest.yaml" -o _release_manifest.yaml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would rather use the rendered version from registry.opensuse.org here, just to avoid the templating issues

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed that will make it simpler

:version-elemental-operator-chart: {{ release_manifest_elemental_version }}
:version-elemental-operator-crds-chart: {{ release_manifest_elemental_crd_version }}
:version-endpoint-copier-operator-chart: {{ release_manifest_eco_version }}
:version-fleet-chart: 108.0.1+up0.14.1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd group all the "manually handled ones" to make them more visible

:version-neuvector-crd-chart: {{ release_manifest_neuvector_crd_version }}
:version-neuvector-dashboard-extension-chart: {{ release_manifest_neuvector_dashboard_version }}
:version-rancher-chart: {{ release_manifest_rancher_version }}
:version-rancher-turtles-chart: 304.0.6+up0.24.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this one should just get replaced with the turtles providers chart.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but I was planning to handle that in #996

VERSIONS_TEMPLATE=${VERSIONS_TEMPLATE:-"../asciidoc/edge-book/versions.adoc.j2"}
VERSIONS_FILE=${VERSIONS_FILE:-"../asciidoc/edge-book/versions.adoc"}
# Generating ${VERSIONS_FILE}
jinja2 ${VERSIONS_TEMPLATE} _release_manifest.yaml | tee ${VERSIONS_FILE}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not fond of the use of jinja2 cli, as it's not packaged in openSUSE.

@@ -0,0 +1,18 @@
#!/usr/bin/env bash
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since we are rendering using python and jinja2, would make it easier to have a python script I think.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah fair point, I can re-write it in python which will probably be cleaner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants