-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use latest tag before non-release version #164
Conversation
Updates the `build-controller-release.sh` script to check for the latest Git tag on the target service controller repository before defaulting the RELEASE_VERSION to `v0.0.0-non-release-version`. This allows developers 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 service controllers that have yet to release any images, the `v0.0.0-non-release-version` continues to be used. Before this patch: ``` [jaypipes@thelio code-generator]$ make build-controller SERVICE=rds building ack-generate ... ok. ==== building rds-controller ==== Copying common custom resource definitions into rds Building Kubernetes API objects for rds Generating deepcopy code for rds Generating custom resource definitions for rds Building service controller for rds Generating RBAC manifests for rds Running gofmt against generated code for rds ==== building rds-controller release artifacts ==== Building release artifacts for rds-v0.0.0-non-release-version Generating common custom resource definitions Generating custom resource definitions for rds Generating RBAC manifests for rds ``` After this patch: ``` [jaypipes@thelio code-generator]$ make build-controller SERVICE=rds building ack-generate ... ok. ==== building rds-controller ==== Copying common custom resource definitions into rds Building Kubernetes API objects for rds Generating deepcopy code for rds Generating custom resource definitions for rds Building service controller for rds Generating RBAC manifests for rds Running gofmt against generated code for rds ==== building rds-controller release artifacts ==== Building release artifacts for rds-v0.0.4 Generating common custom resource definitions Generating custom resource definitions for rds Generating RBAC manifests for rds ``` Note that at this time, the RDS controller's latest published image is `v0.0.4`. Issue #912
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
/lgtm |
/lgtm cancel |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: A-Hilaly, jaypipes The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.