AWS omics documentation change
Summary
Updated branding to 'AWS HealthOmics' and rephrased documentation about call caching. Changed section title to 'Engine-specific caching features'.
Security assessment
Changes are primarily editorial improvements and branding updates without any explicit security context or vulnerability references.
Diff
diff --git a/omics/latest/dev/workflows-call-caching.md b/omics/latest/dev/workflows-call-caching.md index 8283b71ef..bc2000d9c 100644 --- a/omics/latest/dev/workflows-call-caching.md +++ b/omics/latest/dev/workflows-call-caching.md @@ -7 +7 @@ -HealthOmics supports call caching, also known as resume, for private workflows. Call caching saves the outputs of completed workflow tasks after a run finishes. Subsequent runs can use the task outputs from the cache, rather than computing the task outputs again. Call caching reduces compute resource usage, which results in shorter run durations and compute cost savings. +AWS HealthOmics supports call caching, also known as resume, for private workflows. Call caching saves the outputs of completed workflow tasks after a run finishes. Subsequent runs can use the task outputs from the cache, rather than computing the task outputs again. Call caching reduces compute resource usage, which results in shorter run durations and compute cost savings. @@ -9 +9 @@ HealthOmics supports call caching, also known as resume, for private workflows. -You can access the cached task output files after the run completes. During development, if you want to cache intermediate task files to perform advanced debugging and troubleshooting, declare these files as task outputs in the workflow definition. +You can access the cached task output files after the run completes. To perform advanced task debugging and troubleshooting, you can cache intermediate task files by specifying these files as task outputs in the workflow definition. @@ -11 +11 @@ You can access the cached task output files after the run completes. During deve -For production workflows, use call caching to save the completed task results from failed runs. The next run starts from the last successfully completed task, rather than computing the completed tasks again. +You can use call caching to save the completed task results from failed runs. The next run starts from the last successfully completed task, rather than computing the completed tasks again. @@ -19,2 +18,0 @@ If HealthOmics doesn't find a matching cache entry for a task, the run doesn't f - * [Managing your run cache](./workflow-cache-data.html) - @@ -29 +27 @@ If HealthOmics doesn't find a matching cache entry for a task, the run doesn't f - * [Engine-specific features](./workflow-cache-per-engine.html) + * [Engine-specific caching features](./workflow-cache-per-engine.html)