Summary
POST /v1/bundle documents a bundlers query parameter ("Comma-delimited list of bundler types to execute"), but the server never reads it — every bundler runs regardless. The parameter is silently ignored.
Evidence
- Documented:
docs/user/api-reference.md (POST /v1/bundle → Query Parameters table, bundlers row).
pkg/bundler/handler.go: the bundleParams struct has no bundlers/bundler-filter field, and parseQueryParams reads set, dynamic, deployer, node-selector/toleration params, etc. — but never query["bundlers"].
So a request like POST /v1/bundle?bundlers=gpu-operator bundles every component in the recipe, contrary to the docs.
Fix options
- Implement the filter: parse
bundlers, restrict generated output to the named bundler types.
- Or remove
bundlers from the API until implemented.
Docs (#1528) caveat the parameter as "not currently honored" pending this issue.
Summary
POST /v1/bundledocuments abundlersquery parameter ("Comma-delimited list of bundler types to execute"), but the server never reads it — every bundler runs regardless. The parameter is silently ignored.Evidence
docs/user/api-reference.md(POST /v1/bundle → Query Parameters table,bundlersrow).pkg/bundler/handler.go: thebundleParamsstruct has nobundlers/bundler-filter field, andparseQueryParamsreadsset,dynamic,deployer, node-selector/toleration params, etc. — but neverquery["bundlers"].So a request like
POST /v1/bundle?bundlers=gpu-operatorbundles every component in the recipe, contrary to the docs.Fix options
bundlers, restrict generated output to the named bundler types.bundlersfrom the API until implemented.Docs (#1528) caveat the parameter as "not currently honored" pending this issue.