Description of problem:

When you try to export some CV version asynchronously with json format it returns invalid json.

 

How reproducible:

easily

 

Is this issue a regression from an earlier version:

no

 

Steps to Reproduce:

1. Have some repo synced (immediate policy) and a CV with that repo published.

2. Run `hammer content-export complete version --id="<cv_id>" --organization-id="<org_id>" --async`

 

Actual behavior:
You get

{   "message": "Content view version is being exported in task a7045a02-510c-456f-86b6-f6fcea9546f9.",   "id": "a7045a02-510c-456f-86b6-f6fcea9546f9" } {   "message": "Once the task completes the export metadata must be generated with the command:" } {   "message": " hammer content-export generate-metadata --task-id a7045a02-510c-456f-86b6-f6fcea9546f9" }

which is not valid json

 

Expected behavior:

Valid Json, something like

[

{   "message": "Content view version is being exported in task a7045a02-510c-456f-86b6-f6fcea9546f9.",   "id": "a7045a02-510c-456f-86b6-f6fcea9546f9" }

,

{   "message": "Once the task completes the export metadata must be generated with the command:" }

,

{   "message": " hammer content-export generate-metadata --task-id a7045a02-510c-456f-86b6-f6fcea9546f9" }

]

 

Business Impact / Additional info: