-
Notifications
You must be signed in to change notification settings - Fork 39
Introducing buildsign package #1033
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
Introducing buildsign package #1033
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yevgeny-shnaidman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/assign @ybettan |
✅ Deploy Preview for kubernetes-sigs-kmm ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1033 +/- ##
==========================================
- Coverage 79.09% 73.30% -5.80%
==========================================
Files 51 73 +22
Lines 5109 6214 +1105
==========================================
+ Hits 4041 4555 +514
- Misses 882 1471 +589
- Partials 186 188 +2 ☔ View full report in Codecov by Sentry. |
In the current implementation of the build and sign flow, build_sign controller uses 2 packages, build and sign, to verify whether build/sign must be executed, to actually create build/sign pod and to run garbage collector on he successfull pods. In many cases, those 2 packages are very much the same, especially in where the package manager must decide what to do (build pod, delete pod, etc) With the introduction of the MBSC controller, the flow is changing and it makes sense to unify those packages into one package. There is not need to decide if the build/sign should be executed, since that decision is taken by the MIC controller This PR starts with creating the buildsing package and unifying Helper interfaces both in sign and build package into one Helper interface: 1) create Helper interface and implementation for buildsign package 2) move the existing code that was previously using build.Helper and sign.Helper interface to start using unified interface
93f0f8e to
0a0e358
Compare
|
/lgtm |
…netes-sigs#1033) Bumps [github.com/prometheus/client_golang](https://github.com/prometheus/client_golang) from 1.18.0 to 1.19.0. - [Release notes](https://github.com/prometheus/client_golang/releases) - [Changelog](https://github.com/prometheus/client_golang/blob/v1.19.0/CHANGELOG.md) - [Commits](prometheus/client_golang@v1.18.0...v1.19.0) --- updated-dependencies: - dependency-name: github.com/prometheus/client_golang dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
In the current implementation of the build and sign flow, build_sign controller uses 2 packages, build and sign, to verify whether build/sign must be executed, to actually create build/sign pod and to run garbage collector on he successfull pods. In many cases, those 2 packages are very much the same, especially in where the package manager must decide what to do (build pod, delete pod, etc)
With the introduction of the MBSC controller, the flow is changing and it makes sense to unify those packages into one package. There is not need to decide if the build/sign should be executed, since that decision is taken by the MIC controller
This PR starts with creating the buildsing package and unifying Helper interfaces both in sign and build package into one Helper interface: 1) create Helper interface and implementation for buildsign package 2) move the existing code that was previously using build.Helper and
sign.Helper interface to start using unified interface