Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't use the Task object in the dictionary of results for include_role #34461

Merged
merged 1 commit into from
Jan 4, 2018
Merged

Don't use the Task object in the dictionary of results for include_role #34461

merged 1 commit into from
Jan 4, 2018

Commits on Jan 4, 2018

  1. Don't use the Task object in the dictionary of results for include_role 

    The short-circuiting of include_role in TaskExecutor was using the _task object
in the result dictionary. This causes the playbook class to be serialized, which
is something we no longer do due to speed/size problems with nested objects.

Simply removing this should fix a lot of memory and speed problems with include_role.
    @jimi-c
    jimi-c committed Jan 4, 2018
    Configuration menu
    Copy the full SHA
    568a70c View commit details
    Browse the repository at this point in the history