use latest tag before non-release version #164
Merged
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.
Updates the
build-controller-release.sh
script to check for the latestGit tag on the target service controller repository before defaulting
the RELEASE_VERSION to
v0.0.0-non-release-version
. This allowsdevelopers to regenerate their service controllers with new ACK runtimes
without overwriting the static manifests' image versions from the latest
published Git tag to
v0.0.0-non-release-version
. For servicecontrollers that have yet to release any images, the
v0.0.0-non-release-version
continues to be used.Before this patch:
After this patch:
Note that at this time, the RDS controller's latest published image is
v0.0.4
.Issue aws-controllers-k8s/community#912
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.