Update README.md #20885
Merged
Update README.md #20885
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
updated parameter on list keys to get account credentials
jay-most
suggested changes
Apr 7, 2022
There is no parameter named primarykey in the az cli, I have tested the command and it retrieves the key. Also add the comment on the specific line, so it would be easy to resolve there itself. |
kirankumarkolli
approved these changes
Apr 7, 2022
jay-most
approved these changes
May 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
updated parameter on list keys to get account credentials
Packages impacted by this PR
0
Issues associated with this PR
#20669
Describe the problem that is addressed by this PR
This is a mistake in the documentation , instead of documentEndpoint need to replace with primaryMasterKey while fetching credentials using the cli command
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
No, it's just a documentation update
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists