-
Notifications
You must be signed in to change notification settings - Fork 592
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
ApiServerSource stored version v1 and migration tool #4655
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pierDipi 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 |
Codecov Report
@@ Coverage Diff @@
## master #4655 +/- ##
=======================================
Coverage 81.31% 81.31%
=======================================
Files 290 290
Lines 8176 8176
=======================================
Hits 6648 6648
Misses 1128 1128
Partials 400 400
Continue to review full report at Codecov.
|
Having the postinstall package makes sense to me, how did we work around this before? |
We did the same thing, we use this everywhere: https://github.com/knative/eventing/blob/master/config/core/placeholder.go#L17 |
oh, sorry, I means how do we work around other cases that requires post install in upgrade test. I am guessing this is not the first time we need this for upgrade. |
Signed-off-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
1418070
to
7b18c9b
Compare
/retest |
Pinging operation: @houshengbo @Cynocracy LGTM @zhongduo for final LGTM since you've been looking at this one. |
if [ -d "${YAML_REPO_ROOT}/config/post-install" ]; then | ||
|
||
readonly EVENTING_POST_INSTALL_YAML=${YAML_OUTPUT_DIR}/"eventing-post-install.yaml" | ||
|
||
echo "Resolving post install manifests" | ||
|
||
ko resolve ${KO_FLAGS} -f config/post-install/ | "${LABEL_YAML_CMD[@]}" > "${EVENTING_POST_INSTALL_YAML}" | ||
all_yamls+=(${EVENTING_POST_INSTALL_YAML}) | ||
fi |
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.
This will not use our previous naming styple vX.Y.Z
, which makes sense to me but might have some implication of the release tool. So I would like to have someone familiar with the release process to take a look. @n3wscott
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.
@lionelvillard is familiar with the release tool and I tested it before submitting the PR, so we're good to go. :)
(A dir vx.y.z
in a VCS doesn't make any sense to me)
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.
I have to say I totally agree with you! :)
All LGTM other than the change in the hack. I am not familiar wth the tool, so if someone can confirm we want to use it this way and it works with the release bot, I will lgtm. |
/lgtm |
Fixes #4189
Proposed Changes
Release Note