feat: create and manage standalone Holoscan Modules - #220
Conversation
Generate launcher-free Modules with an exact requirements-cli.txt contract, activate metadata-derived project defaults before CLI imports, and reject host or container version drift before lifecycle work.\n\nSupport safe missing, empty, and Git-only creation targets, package the canonical wheelhouse/Docker flow, and cover installed-artifact creation. Co-authored-by: Codex <noreply@openai.com> Signed-off-by: Wenqi Li <wenqil@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Dependency ReviewThe following issues were found:
License Issuessrc/holoscan_cli/setup_scripts/requirements.template.txt
OpenSSF Scorecard
Scanned Files
|
…e-create Signed-off-by: Wenqi Li <wenqil@nvidia.com> # Conflicts: # src/holoscan_cli/setup_scripts/requirements.template.txt
|
Closing this prototype. It demonstrated the standalone-Module idea, and the review feedback here was folded into The work continues on a branch that supersedes this one: it carries these commits plus the |
Summary
This adds a first-class workflow for creating and developing standalone Holoscan Modules with the global
holoscancommand. Module authors no longer need a HoloHub checkout or a repository-localholoscan/holohublauncher.Module workflow
The generated repository includes operator and application examples, Module metadata, CMake and Python packaging support, tests, CI scaffolding, a development Dockerfile, and an exact
requirements-cli.txtcontract.The CLI discovers the Module from its metadata when commands run from the repository root or a nested directory. It also supports explicitly selecting a Module from elsewhere:
Creation can populate a missing destination, an empty directory, or a cloned repository containing only
.git. Existing Git state is preserved, while non-empty destinations are rejected instead of overwritten.Existing HoloHub wrapper behavior and custom Cookiecutter templates remain supported. Creation dependencies stay optional through the
holoscan-cli[create]extra.Validation
AI-assisted: Created with Codex/GPT at the user's request.