Skip to content

Commit 130eb06

Browse files
committed
Reorganizing workflows as feature scenarios.
1 parent 4494f37 commit 130eb06

File tree

171 files changed

+357
-388
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

171 files changed

+357
-388
lines changed

.doc_gen/metadata/medical-imaging_metadata.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1136,7 +1136,7 @@ medical-imaging_Scenario_ImageSetsAndFrames:
11361136
title_abbrev: Get started with image sets and image frames
11371137
synopsis: >
11381138
import DICOM files and download image frames in &AHI;.</para>
1139-
<para>The implementation is structured as a workflow command-line
1139+
<para>The implementation is structured as a command-line
11401140
application.
11411141
synopsis_list:
11421142
- Set up resources for a DICOM import.

.doc_gen/metadata/s3_metadata.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3447,7 +3447,7 @@ s3_Scenario_ObjectLock:
34473447
sdkguide:
34483448
excerpts:
34493449
- description: |
3450-
Entrypoint for the workflow (<noloc>index.js</noloc>). This orchestrates all of the steps.
3450+
Entrypoint for the scenario (<noloc>index.js</noloc>). This orchestrates all of the steps.
34513451
Visit GitHub to see the implementation details for Scenario, ScenarioInput, ScenarioOutput, and ScenarioAction.
34523452
snippet_files:
34533453
- javascriptv3/example_code/s3/scenarios/object-locking/index.js

.doc_gen/metadata/scheduler_metadata.yaml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -156,9 +156,9 @@ scheduler_DeleteScheduleGroup:
156156
- python.example_code.scheduler.DeleteScheduleGroup
157157
services:
158158
scheduler: {DeleteScheduleGroup}
159-
scheduler_ScheduledEventsWorkflow:
160-
title: A complete &EVS; Scheduled Events workflow using an &AWS; SDK
161-
title_abbrev: Scheduled Events workflow
159+
scheduler_ScheduledEventsScenario:
160+
title: A complete &EVS; Scheduled Events scenario using an &AWS; SDK
161+
title_abbrev: Scheduled Events
162162
synopsis_list:
163163
- Deploy a &CFN; stack with required resources.
164164
- Create a &EVS; schedule group.
@@ -173,7 +173,7 @@ scheduler_ScheduledEventsWorkflow:
173173
- sdk_version: 2
174174
github: javav2/example_code/scheduler
175175
excerpts:
176-
- description: Run the workflow.
176+
- description: Run the scenario.
177177
genai: most
178178
snippet_tags:
179179
- scheduler.javav2.scenario.main
@@ -186,7 +186,7 @@ scheduler_ScheduledEventsWorkflow:
186186
- sdk_version: 3
187187
github: dotnetv3/EventBridge Scheduler
188188
excerpts:
189-
- description: Run the workflow.
189+
- description: Run the scenario.
190190
genai: most
191191
snippet_tags:
192192
- Scheduler.dotnetv3.SchedulerWorkflow

.doc_gen/metadata/sesv2_metadata.yaml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -418,17 +418,17 @@ sesv2_DeleteEmailTemplate:
418418
services:
419419
sesv2: {DeleteEmailTemplate}
420420
sesv2_NewsletterWorkflow:
421-
title: A complete &SESv2; Newsletter workflow using an &AWS; SDK
422-
title_abbrev: Newsletter workflow
423-
synopsis: run the &SESv2; newsletter workflow.
421+
title: A complete &SESv2; Newsletter scenario using an &AWS; SDK
422+
title_abbrev: Newsletter scenario
423+
synopsis: run the &SESv2; newsletter scenario.
424424
category: Scenarios
425425
languages:
426426
.NET:
427427
versions:
428428
- sdk_version: 3
429429
github: dotnetv3/SESv2
430430
excerpts:
431-
- description: Run the workflow.
431+
- description: Run the scenario.
432432
genai: most
433433
snippet_tags:
434434
- SESWorkflow.dotnetv3.NewsletterWorkflow

.doc_gen/metadata/sqs_metadata.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -989,10 +989,10 @@ sqs_Scenario_TopicsAndQueues:
989989
github: javascriptv3/example_code/cross-services/wkflw-topics-queues
990990
sdkguide:
991991
excerpts:
992-
- description: This is the entry point for this workflow.
992+
- description: This is the entry point for this scenario.
993993
snippet_tags:
994994
- javascript.v3.wkflw.topicsandqueues.index
995-
- description: The preceding code provides the necessary dependencies and starts the workflow. The next section
995+
- description: The preceding code provides the necessary dependencies and starts the scenario. The next section
996996
contains the bulk of the example.
997997
snippet_tags:
998998
- javascript.v3.wkflw.topicsandqueues.wrapper

.tools/ailly/dotnet-prompts.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,7 @@ code:
152152
153153
'''
154154
/// <summary>
155-
/// Run the preparation step of the workflow. Should return successful.
155+
/// Run the preparation step of the scenario. Should return successful.
156156
/// </summary>
157157
/// <returns>Async task.</returns>
158158
[Fact]

aws-cfn/cross-service/resilient-workflow/resilient-service.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -221,7 +221,7 @@ Resources:
221221
sleep 30 # prevent "Error: Rpmdb changed underneath us"
222222
yum install python-pip -y
223223
python3 -m pip install boto3 ec2-metadata
224-
wget -O server.py https://raw.githubusercontent.com/awsdocs/aws-doc-sdk-examples/main/workflows/resilient_service/resources/server.py
224+
wget -O server.py https://raw.githubusercontent.com/awsdocs/aws-doc-sdk-examples/main/scenarios/features/resilient_service/resources/server.py
225225
python3 server.py 80
226226
227227
# 4. An Auto Scaling group that starts EC2 instances, one in each of three Availability Zones.

cpp/example_code/iot/things_and_shadows_workflow/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
## AWS IoT Things and Shadows Workflow
1+
## AWS IoT Things and Shadows Scenario
22
This example demonstrates various interactions with the AWS Internet of things (IoT) Core service using the AWS SDK.
33
The program guides you through a series of steps, showcasing AWS IoT capabilities and providing a comprehensive example for developers.
44

55

66

7-
### Workflow Steps
7+
### Scenario Steps
88

99
#### Create an AWS IoT thing:
1010

cpp/example_code/medical-imaging/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ This example shows you how to get started using HealthImaging.
9393
#### Get started with image sets and image frames
9494

9595
This example shows you how to import DICOM files and download image frames in HealthImaging.</para>
96-
<para>The implementation is structured as a workflow command-line
96+
<para>The implementation is structured as a command-line
9797
application.
9898

9999

@@ -141,4 +141,4 @@ This example shows you how to import DICOM files and download image frames in He
141141

142142
Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
143143

144-
SPDX-License-Identifier: Apache-2.0
144+
SPDX-License-Identifier: Apache-2.0

cpp/example_code/medical-imaging/imaging_set_and_frames_workflow/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,20 +16,20 @@ This workflow runs as a command-line application prompting for user input.
1616
3. An Amazon S3 output bucket for a DICOM import job.
1717
4. An AWS Identity and Access Management (IAM) role with the appropriate permissions for a DICOM import job.
1818

19-
![CloudFormation stack diagram](../../../../workflows/healthimaging_image_sets/.images/cfn_stack.png)
19+
![CloudFormation stack diagram](../../../../scenarios/features/healthimaging_image_sets/.images/cfn_stack.png)
2020

2121
2. The user chooses a DICOM study to copy from the [National Cancer Institute Imaging Data Commons (IDC) Collections](https://registry.opendata.aws/nci-imaging-data-commons/)' public S3 bucket.
2222
3. The chosen study is copied to the user's input S3 bucket.
2323

24-
![DICOM copy diagram](../../../../workflows/healthimaging_image_sets/.images/copy_dicom.png)
24+
![DICOM copy diagram](../../../../scenarios/features/healthimaging_image_sets/.images/copy_dicom.png)
2525

2626
4. A HealthImaging DICOM import job is run.
2727

28-
![DICOM import diagram](../../../../workflows/healthimaging_image_sets/.images/dicom_import.png)
28+
![DICOM import diagram](../../../../scenarios/features/healthimaging_image_sets/.images/dicom_import.png)
2929

3030
5. The workflow retrieves the IDs for the HealthImaging image frames created by the DICOM import job.
3131

32-
![Image frame ID retrieval diagram](../../../../workflows/healthimaging_image_sets/.images/get_image_frame_ids.png)
32+
![Image frame ID retrieval diagram](../../../../scenarios/features/healthimaging_image_sets/.images/get_image_frame_ids.png)
3333

3434
6. The HealthImaging image frames are downloaded, decoded to a bitmap format, and verified using a CRC32 checksum.
3535
7. The created resources can then be deleted, if the user chooses.

0 commit comments

Comments
 (0)