-
Notifications
You must be signed in to change notification settings - Fork 521
(DOCSP-21766): Added a note about the optional connectionStringSecretName field. #1102
Conversation
|
|
||
| Update the variables in the following command, then run it to retrieve a user's connection strings to the replica set from the secret: | ||
|
|
||
| **NOTE**: The following command requires [jq](https://stedolan.github.io/jq/) version 1.6 or higher.</br></br> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the example on line 51, consider replacing the specific secret variables with a catch-all variable that also covers the note you added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think my comment from the enterprise PR might also apply here
jwilliams-mongo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@corryroot LGTM with one suggestion
mircea-cosbuc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
irajdeep
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Hi @jwilliams-mongo, @mircea-cosbuc, and @irajdeep, I added a note about the optional
connectionStringSecretNamefield.JIRA
All Submissions:
closes #XXXXin your comment to auto-close the issue that your PR fixes (if such).