-
Notifications
You must be signed in to change notification settings - Fork 108
🌱 Split out test modules from capi operator modules #205
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
🌱 Split out test modules from capi operator modules #205
Conversation
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.
/approve
awesome! thank you for doing this.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Fedosin 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 |
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 looks good, apart couple of suggestions:
- since we have separated now test modules into its own folder and we ship it with its own Go module, we most probably should:
- add notes informing about this change properly
- tag and version the new module as part of the release. We would have to create an annotated tag for /test folder and push it every time we do a release from the repo, once this goes in. For example, if we're releasing v0.5.0, we should also tag test/v0.5.0. Also related release docs has to be updated, i.e:
should work.1. Create an annotated tag: - git tag -a -s v0.x.y -m v0.x.y - git tag -a -s test/v0.x.y -m test/v0.x.y 2. Push the tags to the GitHub repository: - git push origin v0.x.y - git push origin test/v0.x.y`
- add a path to new go.mod/sum files in the Makefile
modules
target where we run gomod tidy in all folders where we have go.mod/sum files andverify-modules
target - add it to Dockerfile in https://github.com/kubernetes-sigs/cluster-api-operator/blob/main/Dockerfile#L29-L31
966e394
to
8b902b1
Compare
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
Thanks!
LGTM label has been added. Git tree hash: 77f53d97cb5587ce6707abb261a51c93b4ba16c5
|
/hold |
I don't know if comments from @furkatgofurov7 are blocking so I put the PR on hold, feel free to remove it if needed |
Everything fixed. @furkatgofurov7 I think nothing is pending |
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.
Last nit:
# Create tags locally | ||
# Warning: The test tag MUST NOT be an annotated tag. | ||
git tag -s -a ${RELEASE_TAG} -m ${RELEASE_TAG} | ||
git tag test/${RELEASE_TAG} |
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.
let's sign this tag with gpg signature as above?
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 process is coming from CAPI release document. They explicitly don’t sign test package. I’m not sure why exactly, but I’d rather stick with existing process for now: https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#repeatedly-cut-a-release-1
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 wonder why, though, but it is fine. Thanks!
/lgtm
/hold cancel |
What this PR does / why we need it:
This small change separates capi operator modules from test suite, allowing independent use and external imports. Removes core dependency on capi testing framework. Follows similar pattern to CAPI test suite
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #