/AWS1/IF_OMX=>CREATERUNCACHE()
¶
About CreateRunCache¶
Creates a run cache to store and reference task outputs from completed private runs. Specify an Amazon S3 location where Amazon Web Services HealthOmics saves the cached data. This data must be immediately accessible and not in an archived state. You can save intermediate task files to a run cache if they are declared as task outputs in the workflow definition file.
For more information, see Call caching and Creating a run cache in the Amazon Web Services HealthOmics User Guide.
Method Signature¶
IMPORTING¶
Required arguments:¶
iv_caches3location
TYPE /AWS1/OMXS3URIFORBKTOROBJECT
/AWS1/OMXS3URIFORBKTOROBJECT
¶
Specify the S3 location for storing the cached task outputs. This data must be immediately accessible (not in an archived state).
iv_requestid
TYPE /AWS1/OMXRUNCACHEREQUESTID
/AWS1/OMXRUNCACHEREQUESTID
¶
A unique request token, to ensure idempotency. If you don't specify a token, Amazon Web Services HealthOmics automatically generates a universally unique identifier (UUID) for the request.
Optional arguments:¶
iv_cachebehavior
TYPE /AWS1/OMXCACHEBEHAVIOR
/AWS1/OMXCACHEBEHAVIOR
¶
Default cache behavior for runs that use this cache. Supported values are:
CACHE_ON_FAILURE
: Caches task outputs from completed tasks for runs that fail. This setting is useful if you're debugging a workflow that fails after several tasks completed successfully. The subsequent run uses the cache outputs for previously-completed tasks if the task definition, inputs, and container in ECR are identical to the prior run.
CACHE_ALWAYS
: Caches task outputs from completed tasks for all runs. This setting is useful in development mode, but do not use it in a production setting.If you don't specify a value, the default behavior is CACHE_ON_FAILURE. When you start a run that uses this cache, you can override the default cache behavior.
For more information, see Run cache behavior in the Amazon Web Services HealthOmics User Guide.
iv_description
TYPE /AWS1/OMXUSERCUSTOMDESCRIPTION
/AWS1/OMXUSERCUSTOMDESCRIPTION
¶
Enter a description of the run cache.
iv_name
TYPE /AWS1/OMXUSERCUSTOMNAME
/AWS1/OMXUSERCUSTOMNAME
¶
Enter a user-friendly name for the run cache.
it_tags
TYPE /AWS1/CL_OMXTAGMAP_W=>TT_TAGMAP
TT_TAGMAP
¶
Specify one or more tags to associate with this run cache.
iv_cachebucketownerid
TYPE /AWS1/OMXAWSACCOUNTID
/AWS1/OMXAWSACCOUNTID
¶
The Amazon Web Services account ID of the expected owner of the S3 bucket for the run cache. If not provided, your account ID is set as the owner of the bucket.
RETURNING¶
oo_output
TYPE REF TO /aws1/cl_omxcreateruncachersp
/AWS1/CL_OMXCREATERUNCACHERSP
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
Examples¶
Syntax Example¶
This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.
DATA(lo_result) = lo_client->/aws1/if_omx~createruncache(
it_tags = VALUE /aws1/cl_omxtagmap_w=>tt_tagmap(
(
VALUE /aws1/cl_omxtagmap_w=>ts_tagmap_maprow(
key = |string|
value = new /aws1/cl_omxtagmap_w( |string| )
)
)
)
iv_cachebehavior = |string|
iv_cachebucketownerid = |string|
iv_caches3location = |string|
iv_description = |string|
iv_name = |string|
iv_requestid = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
lv_runcachearn = lo_result->get_arn( ).
lv_runcacheid = lo_result->get_id( ).
lv_runcachestatus = lo_result->get_status( ).
LOOP AT lo_result->get_tags( ) into ls_row.
lv_key = ls_row-key.
lo_value = ls_row-value.
IF lo_value IS NOT INITIAL.
lv_tagvalue = lo_value->get_value( ).
ENDIF.
ENDLOOP.
ENDIF.