You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
revert(secretsmanager): Specify secret value at creation (#9610)
This reverts commit 07fedff.
Further team discussion deemed this feature too dangerous to support within the CDK.
----
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
See [Overview of the Lambda Rotation Function](https://docs.aws.amazon.com/secretsmanager/latest/userguide/rotating-secrets-lambda-function-overview.html) on how to implement a Lambda Rotation Function.
106
80
107
81
### Rotating database credentials
108
-
109
82
Define a `SecretRotation` to rotate database credentials:
110
-
111
83
```ts
112
84
newSecretRotation(this, 'SecretRotation', {
113
85
application: SecretRotationApplication.MYSQL_ROTATION_SINGLE_USER, // MySQL single user scheme
@@ -118,7 +90,6 @@ new SecretRotation(this, 'SecretRotation', {
118
90
```
119
91
120
92
The secret must be a JSON string with the following format:
121
-
122
93
```json
123
94
{
124
95
"engine": "<required: database engine>",
@@ -132,7 +103,6 @@ The secret must be a JSON string with the following format:
132
103
```
133
104
134
105
For the multi user scheme, a `masterSecret` must be specified:
test.equals(secret.node.metadata[0].data,'Using a `secretString` value which will be visible in plaintext in the CloudFormation template and cdk output.');
594
-
595
-
test.done();
596
-
},
597
-
598
-
'throws when specifying secretString and generateStringKey'(test: Test){
0 commit comments