Wrong Parameter Name when creating an AppRole#8818
Conversation
"token_policies" parameter does not work when creating an AppRole. If you use this parameter name, you are not able to create an AppRole attached to the policy that you have specified along with this parameter. Instead, I've changed this parameter name to "policies" and it works. So, the documentation was not up to date, I've changed this info so users will not be confused.
|
Hi @mikail-gultekin, Thank you for the PR! I suspect you're using an older Vault version than the latest, which is what the website documentation targets. I think it's a good idea to document the deprecated option too, though it should be flagged as such and a note added to recommend the newer option that replaces it. I don't think it should appear in the example however, so please revert that part. |
Hi folks! I'm going to go ahead and close this PR - please feel free to re-open it (and rebase off of main) if the questions can be answered and you'd like to continue working on it. Thanks! |
…shicorp#8818) Co-authored-by: John-Michael Faircloth <fairclothjm@users.noreply.github.com>
"token_policies" parameter does not work when creating an AppRole. If you use this parameter name, you are not able to create an AppRole attached to the policy that you have specified along with this parameter. Instead, I've changed this parameter name to "policies" and it works. So, the documentation was not up to date, I've changed this info so users will not be confused.