Project

General

Profile

Actions

Bug #10114

closed

Allow relay-api to make asynchronous remote run call with output

Added by Vincent MEMBRÉ about 7 years ago. Updated about 7 years ago.

Status:
Released
Priority:
N/A
Category:
API
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Currently we always wait for output even if we put the asynchronous parameter in the request.

Some documentation on achieving this:

https://mortoray.com/2014/03/04/http-streaming-of-command-output-in-python-flask/
http://flask.pocoo.org/docs/0.12/patterns/streaming/
https://docs.python.org/2/library/subprocess.html#subprocess.Popen


Subtasks 2 (0 open2 closed)

Bug #10136: apply policy should use asynchronous call when getting output of one nodeReleasedFrançois ARMAND2017-02-03Actions
Bug #10154: Asynchronous on node behing a relay does not work quite wellReleasedBenoît PECCATTE2017-02-08Actions
Actions #1

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.0~beta2 to 4.1.0~beta3
Actions #2

Updated by Vincent MEMBRÉ about 7 years ago

  • Status changed from New to In progress
Actions #3

Updated by Vincent MEMBRÉ about 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1243
Actions #4

Updated by Vincent MEMBRÉ about 7 years ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by Vincent MEMBRÉ about 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.0~beta3 which was released today.

Actions

Also available in: Atom PDF