Skip to content

Commit 6200ea8

Browse files
authored
style: improve clarity on aws changes (#3623)
Signed-off-by: Samantha Coyle <[email protected]>
1 parent 72c92fb commit 6200ea8

File tree

2 files changed

+5
-4
lines changed

2 files changed

+5
-4
lines changed

.build-tools/builtin-authentication-profiles.yaml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,12 @@ aws:
1111
example: '"us-east-1"'
1212
- name: accessKey
1313
description: AWS access key associated with an IAM account
14-
required: true
14+
required: false
1515
sensitive: true
1616
example: '"AKIAIOSFODNN7EXAMPLE"'
1717
- name: secretKey
1818
description: The secret key associated with the access key
19-
required: true
19+
required: false
2020
sensitive: true
2121
example: '"wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"'
2222
- name: sessionToken
@@ -41,6 +41,7 @@ aws:
4141
description: |
4242
IAM role that has access to AWS resource.
4343
This is another option to authenticate with MSK and RDS Aurora aside from the AWS Credentials.
44+
This will be marked required in Dapr 1.17.
4445
example: '"arn:aws:iam::123456789:role/mskRole"'
4546
- name: sessionName
4647
type: string
@@ -51,7 +52,7 @@ aws:
5152
- title: "AWS: Credentials from Environment Variables"
5253
description: Use AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY from the environment
5354
- title: "AWS: IAM Roles Anywhere"
54-
description: Use X.509 certificates to establish trust between AWS and your AWS account and the Dapr cluster using AWS IAM Roles Anywhere.
55+
description: Use X.509 certificates to establish trust between your AWS account and the Dapr cluster using AWS IAM Roles Anywhere.
5556
metadata:
5657
- name: trustAnchorArn
5758
description: |

pubsub/kafka/metadata.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ builtinAuthenticationProfiles:
4545
required: false
4646
sensitive: true
4747
description: |
48-
This maintains backwards compatibility with existing fields.
48+
This maintains backwards compatibility with existing fields.
4949
It will be deprecated as of Dapr 1.17. Use 'secretKey' instead.
5050
If both fields are set, then 'secretKey' value will be used.
5151
The secret key associated with the access key.

0 commit comments

Comments
 (0)