Summary
Append the AWS solution-tracking metrics identifier (uksb-wt64nei4u6) to the CloudFormation stack description so deployments of this sample are counted via AWS's standard usage-tracking mechanism.
Background
AWS samples/solutions embed a uksb-* tracking token in the stack description to record anonymized deployment metrics. This stack currently sets a plain description (cdk/src/main.ts:41):
description: 'ABCA Development Stack',
Acceptance criteria
Coupling note (must address before/with the cleanup-script branch)
The in-flight feat/cleanup-ephemeral-stacks branch (PR #109) matches ABCA stacks by an exact description string ([[ "$DESCRIPTION" != "ABCA Development Stack" ]]). Appending the tracking ID changes the description and will break that exact match once both land. When the cleanup script merges, its matcher must switch to a prefix match (e.g. == "ABCA Development Stack"*). Tracking here so it isn't missed.
Summary
Append the AWS solution-tracking metrics identifier
(uksb-wt64nei4u6)to the CloudFormation stack description so deployments of this sample are counted via AWS's standard usage-tracking mechanism.Background
AWS samples/solutions embed a
uksb-*tracking token in the stack description to record anonymized deployment metrics. This stack currently sets a plain description (cdk/src/main.ts:41):Acceptance criteria
ABCA Development Stack (uksb-wt64nei4u6)Coupling note (must address before/with the cleanup-script branch)
The in-flight
feat/cleanup-ephemeral-stacksbranch (PR #109) matches ABCA stacks by an exact description string ([[ "$DESCRIPTION" != "ABCA Development Stack" ]]). Appending the tracking ID changes the description and will break that exact match once both land. When the cleanup script merges, its matcher must switch to a prefix match (e.g.== "ABCA Development Stack"*). Tracking here so it isn't missed.