Add Hydra Config support for UI scripts #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We currently use
argparsers, but as we land more pipeline features, this will grow unwieldy and we'll want a unified config for controlling all the individual agent components.This PR adds an initial Hydra setup and migrates the existing UI clis (pipeline-ui, fuser-ui, kernel-agent).
Hydra integration for other scripts will be in follow up PRs
Note: We can follow up this PR to use StructuredConfigs once the cli is a bit more stable
Note 2: I'm not 100% sold that I want to use Hydra, but it's a simple onramp/offramp if we want to use something else (Fiddle, manual dataclass factories, etc.) and it's better than manual parsing
Manual tests
scripts/triton_ui.pyscripts/pipeline_ui.pyscripts/fuser_ui.pyExample Output (Similar across scripts)