Avoid double v prefix in the AppList #2123
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
absoludity
approved these changes
Oct 22, 2020
script/chart_sync_utils.sh
Outdated
| @@ -71,6 +71,7 @@ replaceImage() { | |||
| updateRepo() { | |||
| local targetRepo=${1:?} | |||
| local targetTag=${2:?} | |||
| local targetTagWithoutV=${targetTag/v/} | |||
There was a problem hiding this comment.
A bit pedantic, but you probably want to strip from the front of the var, rather than replacing anywhere in the var?
$ VERSIONTEST=v1.2.3 && echo ${VERSIONTEST#v}
1.2.3
$ VERSIONTEST=1.2.3v && echo ${VERSIONTEST#v}
1.2.3v
$ VERSIONTEST=1.2.3v && echo ${VERSIONTEST/v/}
1.2.3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
The appVersion field in the
Chart.yamlmay contain already thevprefix, and we are prefixing anothervagain:In any case, the
appVersiondoesn't need that prefix so I am also removing it from our chart release process.Applicable issues
I'd swear I fixed this already but I couldn't find it, maybe I forgot to create the PR 馃