init for chart version updates #14
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "update-charts-version"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
lgtm other than the comment re subcharts, IMO we should avoid changing those if it's not needed so rebasing against upstream versions is easier.
@ -7,3 +7,3 @@
name: baremetal-operator
repository: file://./charts/baremetal-operator
version: 0.5.0
version: 302.0.0_up0.5.0
Do we need to update the sub-chart versions? AFAICS we don't and this will make rebasing to new versions from upstream more difficult?
I was not sure if we wanted to upgrade them and I agree with your point so will revert the sub-charts.
We may need to do some testing but do we also want to align the
BuildTag
as helm says:I adopted that approach in the metal3/turtles PRs just pushed, but we can test/discuss before aligning here.
8b133980be
toe31fc75572
e31fc75572
to2fe0c8280a
I updated this PR following your approach for the BuildTag.
@ -1,5 +1,5 @@
#!BuildTag: %%IMG_PREFIX%%akri-dashboard-extension-chart:1.2.0
#!BuildTag: %%IMG_PREFIX%%akri-dashboard-extension-chart:1.2.0-%RELEASE%
#!BuildTag: %%IMG_PREFIX%%akri-dashboard-extension-chart:302.0.0_up1.1.0
#!BuildTag: %%IMG_PREFIX%%akri-dashboard-extension-chart:302.0.0_up1.1.0-%RELEASE%
This needs rebasing on the version update from @jtomasek
@ -16,3 +16,3 @@
name: mariadb
repository: file://./charts/mariadb
version: 0.5.4
version: 302.0.0_up0.5.4
This is a subchart reference and should not be updated
@ -18,3 +18,3 @@
name: akri-dashboard-extension
type: application
version: 1.2.0
version: 302.0.0+up1.1.0
Same as above, needs updating to 1.2.0
Couple of remaining issues, otherwise lgtm
2fe0c8280a
todfd55917f2
dfd55917f2
to3543bbe39e
All issues resolved now.
LGTM overall, I however think we should have them be some kind of template here to make it easier for us, something like
%%CHART_MAJOR%%.X.Y
and have OBS to replace it to302
in the 3.2 branch and say999
in Factory, this way we don't have to do anything when cutting a new release branch here3543bbe39e
toa66325901d
@ -14,3 +14,3 @@
apiVersion: v2
appVersion: 1.2.0
description: 'SUSE Edge: Akri extension for Rancher Dashboard'
description: "SUSE Edge: Akri extension for Rancher Dashboard"
Not sure why the quoting changed as seems unrelated to the version updates?
This is caused by my auto formatter. It is set to use double quotes for these types of files.