feat: Add flexible commandArgs support for complete Feast CLI control #5678
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.
What this PR does / why we need it:
commandArgsparameter that allows complete control over Feast CLI command-line arguments--root_path,--registry_ttl_sec, custom ports, and future optionsCreates a future-proof solution that doesn't require template updates for new Feast CLI features
The current Feast Helm chart limits configurability by hardcoding CLI arguments. This creates several problems:
--root_pathfor UI proxy support, --registry_ttl_secfor registry refresh control)Inflexibility: Complex deployment scenarios requiring custom argument ordering or conditional options are impossible
This PR allows for flexible, comprehensive solution that will grow with Feast's capabilities while preserving existing functionality.
Which issue(s) this PR fixes:
None
Misc
None