⚠️ Plugin chaining

[Adirio]

Plugin phase 1.5

Implements #1990
Closes: #2036

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[camilamacedo86]

The scenario operator-framework/operator-sdk#4581 (comment) needs also be solved before we get it merged.

[Adirio]

After rebasing when #2037 got merged, go mod tidy is bumping the dependencies in the declarative projects when it should not. The only difference from non-declarative projects is relation to modules is the import of kubernetes-sigs/kubebuilder-declarative-pattern. Any way to prevent this in combination with go mod tidy to bump all those dependencies?

[Adirio]

After rebasing when #2037 got merged, go mod tidy is bumping the dependencies in the declarative projects when it should not. The only difference from non-declarative projects is relation to modules is the import of kubernetes-sigs/kubebuilder-declarative-pattern. Any way to prevent this in combination with go mod tidy to bump all those dependencies?

I discovered the cause. go post-scaffold method was running go mod tidy and declarative post-scaffold method was running go get kubernetes-sigs/kubebuilder-declarative-pattern@.... As the go mod tidy was being run before go get ... it was importing the latest version of kubebuilder-declarative-pattern which bumped a bunch of versions. Later go get ... was defining the exact declarative pattern version but the damage was already done. Changing go get ... calls to the end of scaffold hooks instead of post-scaffold guarantees that they will all be run before go mod tidy.

[Adirio]

/close

Closing this in favor of the chain of PRs #2057 - #2058 - #2059 that split this PR into several PRs to split concerns and make reviewer job easier.

[k8s-ci-robot]

@Adirio: Closed this PR.

In response to this:

/close

Closing this in favor of the chain of PRs #2057 - #2058 - #2059 that split this PR into several PRs to split concerns and make reviewer job easier.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.