New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pipeMode
Parameter to EvalCommand
#336
Labels
feat
New feature or request
Comments
Development Plan
Questions
configu eval --schema './schema1.cfgu.json' | configu eval --schema './schema2.cfgu.json' --pipe-mode 'forward' | configu eval --schema './schema3.cfgu.json'
Unit TestsValid Tests
Notes / Comments / Additional |
1 task
1 task
@RonConfigu, I guess you forgot to tag me on the questions part, but to address your query: No, each |
@configu/dev decided to reproductize this feature. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suggestion
Introducing a
pipeMode
parameter to theEvalCommand
. This parameter will control how the output of oneeval
command is used when piped into another command. ThepipeMode
parameter will accept two values:forward
: The output of theeval
command is only passed forward to the next command in the pipeline, for template evaluation etc, but not included in theexport
result.include/merge
: The output is included in theexport
result. default mode.override
: TBD @rannn505This addition would look like this in practice:
Motivation
The
pipeMode
parameter enhances the flexibility of theEvalCommand
, allowing users to precisely control how outputs are handled in piped sequences. This is particularly useful in complex configuration environments where differenteval
commands need to be chained together, yet the inclusion of each command's output in the final result needs to be selectively determined. By introducingpipeMode
, we cater to a wider range of user requirements and make the CLI more versatile for various deployment and configuration scenarios.Context
The text was updated successfully, but these errors were encountered: