You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ansible Module utils do not provide any mechanism for controlling STDOUT prints for custom written modules. We can scrap verbosity level (from -vvv flags), so we can enhance our custom developers logger now.
But for printing, we have no access to Ansible class Display from utils for Ansible Core. Guess there were reasons why they didn't provide it for the custom modules - but don't know yet why. And don't know how to overcome it easily.
Please describe the solution you'd like
Enable printing STDOUT (like some waiting time, retries etc.)
Additional context
No response
The text was updated successfully, but these errors were encountered:
Please describe the problem
Ansible Module utils do not provide any mechanism for controlling STDOUT prints for custom written modules. We can scrap verbosity level (from -vvv flags), so we can enhance our custom developers logger now.
But for printing, we have no access to Ansible class Display from utils for Ansible Core. Guess there were reasons why they didn't provide it for the custom modules - but don't know yet why. And don't know how to overcome it easily.
Please describe the solution you'd like
Enable printing STDOUT (like some waiting time, retries etc.)
Additional context
No response
The text was updated successfully, but these errors were encountered: