rtk-ai/rtk

Bug: string instead of "DynamoDBFullAccessInline"

Open

#1228 opened on Apr 11, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
bugeffort-smallfilter-qualitygood first issue

Description

Bug description

Raw command

> aws iam list-user-policies --user-name gekh
{
    "PolicyNames": [
        "DynamoDBFullAccessInline"
    ]
}

With RTK proxy:

> rtk aws iam list-user-policies --user-name gekh
{
  PolicyNames:
  [
    string
  ]
}

expected:

DynamoDBFullAccessInline

How to reproduce

First create a file ddb-full-access-inline.json:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "dynamodb:*",
      "Resource": "*"
    }
  ]
}

and run

aws iam put-user-policy \
  --user-name [REPLACE_WITH_USERNAME] \
  --policy-name DynamoDBFullAccessInline \
  --policy-document file://ddb-full-access-inline.json

after creation run thic command

rtk aws iam list-user-policies --user-name [REPLACE_WITH_USERNAME]

Contributor guide

Tech stack
rustaws
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic RustJSON handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Investigate the code that prints the command output, likely in the main response handling module. Look for where JSON values are serialized to string, as the issue shows that the actual string value is replaced with the Rust debug representation 'string'. Check if the output uses {:?} instead of {} or if there is a custom serializer that incorrectly handles string literals. Also search for any similar issues in the repository.