Mellanox / network-operator-init-container / 24659771709

65%

main: 65%

Build Type

Pull #105

github

Committed by almaslennikov

Commit Message

Refactor pre-flight checks to env-var-driven module lists with warn-by-default semantics

Align the pre-flight dependency check with doca-driver-build's env-var-driven
configuration pattern and change the default failure mode from blocking to
warning.

- Replace the package-level KnownThirdPartyRDMAModules and KnownStorageModules
  maps with caarlos0/env/v11-tagged slices on ModuleDependencyCheckConfig.
  STORAGE_MODULES and THIRD_PARTY_RDMA_MODULES now drive classification with
  colon-separated defaults that mirror doca-driver-build exactly, so adding a
  module to one side no longer requires a Go-code change on the other.
- Add ib_iser and ib_srp to the default storage list, fixing the Ubuntu 24.04
  regression where ib_iser loaded as an unknown blocking module.
- Gate the pre-flight check's blocking behavior on a new
  BLOCK_ON_PREFLIGHT_CHECKS env var (default false). Findings are logged at
  warning level and init proceeds unless operators opt in to strict mode.
- Drop the ModuleDependencyCheck.Enable field. The check always runs; if no
  Modules are configured it is silently skipped.
- Extend NewChecker to accept the third-party and storage module lists so the
  caller controls classification instead of relying on global state.

Signed-off-by: Alexander Maslennikov <amaslennikov@nvidia.com>

Pull Request Pull Request #105: Refactor pre-flight checks to env-var-driven module lists with warn-by-default semantics

Coverage Stats

71 of 92 new or added lines in 3 files covered. (77.17%)

36 existing lines in 2 files now uncovered.

390 of 607 relevant lines covered (64.25%)

13.83 hits per line