def view_transform_tasks_launch(request):
u"""Launch a transformation task."""
try:
auth_user = request.args.get(u'ebuio_u_pk') or request.form.get(u'ebuio_u_pk')
data = get_request_data(request, qs_only_first_value=True)
task_id = api_core.launch_transform_task(
user_id=auth_user, media_in_id=data[u'media_in_id'], profile_id=data[u'profile_id'],
filename=data[u'filename'], metadata={u'title': data[u'title']}, send_email=False, queue=data[u'queue'],
callback_url=u'/transform/callback')
return {u'task_id': task_id}
except Exception as e:
logging.exception(e)
return {u'errors': [unicode(e)]}
def api_transform_task_post(auth_user=None, api_core=None, request=None):
u"""
Launch a transformation task.
Any user can launch a transformation task using any media asset as input and any transformation profile.
This is linked to media assets and transformation profile API methods access policies.
The output media asset is registered to the database with the PENDING status and the ``parent_id`` field is set to
input media asset's ``id``. This permit to know relation between media assets !
The orchestrator will automatically add ``add_date`` to ``statistic``.
.. note::
Interesting enhancement would be to :
* Schedule obs by specifying start time (...) ;
* Handle the registration of tasks related to PENDING medias ;
"""
data = get_request_data(request, qs_only_first_value=True)
task_id = api_core.launch_transform_task(
auth_user._id, data[u'media_in_id'], data[u'profile_id'], data[u'filename'], data[u'metadata'],
data[u'send_email'], data[u'queue'], u'/transform/callback')
return ok_200(task_id, include_properties=True)
