Skip to content

Commit 764d078

Browse files
committed
Added the ability to read in the partnersTable from a DynamoDB.
1 parent 47165d9 commit 764d078

File tree

1 file changed

+2
-0
lines changed
  • Management-Utilities/auto_create_sm_relationships

1 file changed

+2
-0
lines changed

Management-Utilities/auto_create_sm_relationships/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ There are a few things you need to do in order to get this script to run properl
2525
- partnerFsxnIP - Set to the IP address of the management port of the partner FSxN file system.
2626
- partnerSvmName - The name of the SVM where you want the SnapMirror destination volume to reside.
2727
- partnerSvmSourceName - Is the "peered name" of the source SVM. Usually, it is the same as the source SVM, but can be different if that same name already exists on the partner file system. When you peer the SVM it will require you to create an alias for the source SVM so all the SVM names are unique.
28+
2829
*NOTE:* Instead of defining the partnersTable in the script, you can define dynamodbPartnersTableName and dynamodbRegion and the script will read in the partner information from the specified DynamoDB table. The partners table should have the following fields:
2930
- soureceId - Which is the concatentation of the source file system ID followed by a ":" followed by the SVM name. It is done this way because the id has to be unique in the table. It is split up into its two components in the script when it is read in.
3031
- partnerFsxnIp - Set to the IP address of the management port of the partner FSxN file system.
@@ -36,6 +37,7 @@ There are a few things you need to do in order to get this script to run properl
3637
- secretName - Set to the name of the secret created in step one.
3738
- usernameKey - Set to the name of the key that holds the username.
3839
- passwordKey - Set to the name of the key that holds the password.
40+
3941
*NOTE:* Instead of defining the secretsTable in the script, you can define dynamodbSecretsTableName and dynamodbRegion and the script will read in the secretsTable information from the specified DynamoDB table. The table should have the same fields as the secretsTable defined above.
4042

4143
- secretsManagerRegion - Set to the region where the Secrets Manager has been set up.

0 commit comments

Comments
 (0)