We will need to provide distinctive/unique step_id/step_name in
order to make use of the Shipyard logs API/CLI. It is found during
testing that 'deckhand_get_design_version' is used as both the name
of the subdag as well as 'task_id' [0]. As such, we will only be able
to retrieve the logs of the subdag when we run a query with step_id as
'deckhand_get_design_version'.
This is an issue and hence we will change the name of the subdag so that
it is different from the task_id. In this way we will be retrieve the logs
for the subdag as well as the task.
[0] Current output of describe step (note the name of the steps in failed state):
Steps Index State
step/01CAYXMTK1ECXBK0SF4MQBYEND/action_xcom 1 success
step/01CAYXMTK1ECXBK0SF4MQBYEND/dag_concurrency_check 2 success
step/01CAYXMTK1ECXBK0SF4MQBYEND/preflight 3 success
step/01CAYXMTK1ECXBK0SF4MQBYEND/deckhand_get_design_version 4 failed
step/01CAYXMTK1ECXBK0SF4MQBYEND/dag_deployment_configuration 5 upstream_failed
step/01CAYXMTK1ECXBK0SF4MQBYEND/validate_site_design 6 upstream_failed
step/01CAYXMTK1ECXBK0SF4MQBYEND/deckhand_get_design_version 7 failed
step/01CAYXMTK1ECXBK0SF4MQBYEND/drydock_build 8 upstream_failed
step/01CAYXMTK1ECXBK0SF4MQBYEND/ucp_preflight_check 9 success
step/01CAYXMTK1ECXBK0SF4MQBYEND/k8s_preflight_check 10 success
step/01CAYXMTK1ECXBK0SF4MQBYEND/shipyard_retrieve_rendered_doc 11 upstream_failed
step/01CAYXMTK1ECXBK0SF4MQBYEND/armada_build 12 upstream_failed
Change-Id: I191cb8509c8d3d8e63f539b25c1693e9b8794aac
f8fb44b7a0