Skip to content

Commit ecbe260

Browse files
committed
chore(dynamodb): rename throttle attack label to "Change Read/Write Table Capacity"
1 parent 6843e9e commit ecbe260

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

charts/steadybit-extension-aws/Chart.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
apiVersion: v2
22
name: steadybit-extension-aws
33
description: Steadybit AWS extension Helm chart for Kubernetes.
4-
version: 2.2.27
4+
version: 2.2.28
55
appVersion: v2.4.14
66
home: https://www.steadybit.com/
77
icon: https://steadybit-website-assets.s3.amazonaws.com/logo-symbol-transparent.png

extdynamodb/table_attack_throttle.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ func (a *tableThrottleAttack) NewEmptyState() TableThrottleAttackState {
4747
func (a *tableThrottleAttack) Describe() action_kit_api.ActionDescription {
4848
return action_kit_api.ActionDescription{
4949
Id: fmt.Sprintf("%s.throttle", tableTargetId),
50-
Label: "Trigger AWS DynamoDB Table Throttle",
50+
Label: "Change Read/Write Table Capacity",
5151
Description: "Temporarily lowers a PROVISIONED-mode DynamoDB table's read + write capacity (and the capacity of each GSI) to force ProvisionedThroughputExceededException. " +
5252
"Validates client retry / backoff logic and circuit breakers. Original capacities are restored on stop. " +
5353
"Tables in PAY_PER_REQUEST mode are not supported (no fixed capacity to lower). If the table has Application Auto Scaling, the autoscaler will eventually scale back up; " +

0 commit comments

Comments
 (0)