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
runners when executed in jinja templates should not print out to stdout #28354
Comments
@arthurlogilab, thanks for the report. |
👍 This is happening to me when using saltutil.runner under orchestrator. Can you hint where this can be potentially happening. I am will to take a look and see if I can propose a PR |
@gmolight, I am not sure where to look, but I would probably start with |
thanks, I will take a look if I find something I will post here and if a solution I will send PR |
FYI, here is the stacktrace after I traced the problem:
I'm not sure I understand everything yet but it's seems there's an event triggered after the completion of the Another stacktrace, maybe more useful:
I'm using a configuration where I have a pillar filled with the result of a If I set |
Another comment: the extra output I get when running an orchestration seems to come from the fact that I'm using I still don't understand how everything fits together... |
I'm still facing this issue on a daily basis. More info though:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
I have some jinja templates that run some salt runners like this :
This ends up spewing out a bunch of output when being rendered. It would be nice if was quiet.
The text was updated successfully, but these errors were encountered: