airship
/
shipyard
Code Issues Proposed changes
shipyard/src/bin/shipyard_airflow/shipyard_airflow/control/action
History
Andrey Volkov 0e6486be8b Return non-200 response if Airflow log request failed 
This patch modifies API behavior for
GET /v1.0/actions/{action_id}/steps/{step_id}/logs
such way:
- it returns the same status code as Airflow HTTP request returned
  if Airflow responds with a status code of 400 or greater,
- it returns 500 error status code if an exception happens during
  Airflow HTTP request (200 was before).

Warning: this change breaks API backward compatibility, now a client
could get 4xx or 5xx codes proxied from Airflow.

Change-Id: Ic5dceb3abc34415d21b4d8d4e71b4e5661a7363d
 		2018-10-04 07:23:21 -07:00
..
__init__.py Refactor shipyard to UCP target layout 2018-04-24 16:47:13 -05:00
action_validators.py Add redeploy_server processing 2018-08-21 09:42:40 -05:00
actions_api.py Add relabel_nodes action 2018-09-25 07:34:43 -05:00
actions_control_api.py Refactor policies to use constant values 2018-08-08 10:58:55 -05:00
actions_id_api.py Refactor policies to use constant values 2018-08-08 10:58:55 -05:00
actions_steps_id_api.py Refactor policies to use constant values 2018-08-08 10:58:55 -05:00
actions_steps_id_logs_api.py Return non-200 response if Airflow log request failed 2018-10-04 07:23:21 -07:00
actions_validations_id_api.py Refactor policies to use constant values 2018-08-08 10:58:55 -05:00