IAM Client get_user_policy documentation inaccurate
See original GitHub issueDescribe the bug
Boto3 version 1.17.24 IAM Client get_user_policy method return values are incorrect in the documentation. The documentation states that the PolicyDocument
in the return object is string
, but the observed values is dict
.
Steps to reproduce Code:
import boto3
iam_client = boto3.client('iam')
user_policy = iam_client.get_user_policy(
UserName=username,
PolicyName=policy_name,
)
print(type(user_policy))
<class 'dict'>
I would be happy to provide a PR to update the documentation, if the actual behavior is correct, and if I could get a pointer to where the documentation lives in this repo.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
ListUserPolicies - AWS Identity and Access Management
Lists the names of the inline policies embedded in the specified IAM user. An IAM user can also have managed policies attached to...
Read more >class IAM. Client - Boto3 Docs 1.26.33 documentation
A low-level client representing AWS Identity and Access Management (IAM) ... Returns: True if the operation can be paginated, False otherwise.
Read more >Documentation incorrect regarding IAM policy ...
Describe the bug The Boto3 IAM documention for the client methods all state that the policy document is returned as a string data...
Read more >iam
Package iam provides the API client, operations, and parameter types for AWS Identity ... User Guide (https://docs.aws.amazon.com/IAM/latest/UserGuide/).
Read more >aws iam update-account-password-policy
& * ( ) _ + - = [ ] { } | ' If you do not specify a value for this...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@bosatsu,
I think we’ll leave this open for tracking purposes for the time being. Thanks again for reporting this!
@stobrien89 Sounds good. Not sure if you want to keep this open for tracking, but if not feel free to close it.