Skip to content

remove bundle injection, make golangci-lint config consistent #145

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

Merged

Conversation

joelanford
Copy link
Member

@joelanford joelanford commented Apr 25, 2024

The primary purpose of this PR is to make the golangci-lint config consistent across repo.

One issue that turned up was around complexity with some code related to injecting bundles via the old sqlite dynamic pod injection technique. Rather than spending the time making that code less complex, I removed it. That's because we've moved on to FBC catalogs and that code is obsolete. It's flags have also always been hidden, so there is little risk of breakage.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 25, 2024
@joelanford joelanford force-pushed the consistent-golangci-lint-config branch from 001bb62 to a6286fb Compare April 25, 2024 14:34
@joelanford joelanford marked this pull request as ready for review April 25, 2024 14:38
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 25, 2024
@openshift-ci openshift-ci bot requested review from benluddy and jmrodri April 25, 2024 14:38
@grokspawn grokspawn added this pull request to the merge queue Apr 25, 2024
Merged via the queue into operator-framework:main with commit 1d9a076 Apr 25, 2024
4 checks passed
@joelanford joelanford deleted the consistent-golangci-lint-config branch November 1, 2024 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants