We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
eval always namespaces the variable names, regardless of jmespath selection scope
bash-3.2$ cat test.yml foo: bar: baz: "something" bash-3.2$ python3 -m niet . test.yml foo: bar: baz: something bash-3.2$ python3 -m niet . test.yml -f eval foo__bar__baz="something" bash-3.2$ python3 -m niet .foo.bar test.yml baz: something bash-3.2$ python3 -m niet .foo.bar test.yml -f eval foo_bar__baz="something" bash-3.2$
i.e. expected output for:
python3 -m niet .foo.bar test.yml -f eval
would be
baz="something"
The text was updated successfully, but these errors were encountered:
a workaround is to output as flat yaml, and pipe back to niet:
$ niet .foo.bar test.yml | niet . -f eval baz="something"
Sorry, something went wrong.
Hello,
Thanks to have reported this issue. I'll try to check why this happen.
Hervé
I agree that, from a functional point of view, the variable name should be related to the given scope.
No branches or pull requests
eval always namespaces the variable names, regardless of jmespath selection scope
i.e. expected output for:
would be
The text was updated successfully, but these errors were encountered: