API: Introduce Results object
Rationale: - results inpection of single run_command or actions Main Changes: - In order to catch the individual results when using the actions context manager run_play is used internally instead of run_ansible (everything must stay within the process memory). The caveat is that fact gathering for /actions/ is now all or nothing (IMO nobody was using this feature anyway)
Showing
- enoslib/api.py 161 additions, 68 deletionsenoslib/api.py
- enoslib/config.py 7 additions, 2 deletionsenoslib/config.py
- enoslib/html/__init__.py 84 additions, 43 deletionsenoslib/html/__init__.py
- enoslib/html/style.css 5 additions, 4 deletionsenoslib/html/style.css
- enoslib/infra/configuration.py 2 additions, 1 deletionenoslib/infra/configuration.py
- enoslib/infra/enos_iotlab/sensor.py 2 additions, 1 deletionenoslib/infra/enos_iotlab/sensor.py
- enoslib/objects.py 22 additions, 11 deletionsenoslib/objects.py
- enoslib/service/locust/locust.py 25 additions, 14 deletionsenoslib/service/locust/locust.py
- enoslib/tests/functionnal/test_static_run_ansible.py 2 additions, 2 deletionsenoslib/tests/functionnal/test_static_run_ansible.py
- enoslib/tests/functionnal/test_static_run_command.py 5 additions, 6 deletionsenoslib/tests/functionnal/test_static_run_command.py
- enoslib/tests/unit/test_api.py 40 additions, 7 deletionsenoslib/tests/unit/test_api.py
Loading
Please register or sign in to comment