Skip to content

-s in secrets engine makes them unreadable #240

Description

@mike-bailey

At least the Logical endpoints improperly URL encodes - and thus if you have something, say, called secrets-kv it won't be able to list, read, etc as it'll encode - and fail. Vault CLI doesn't encode -.

I tapped the list functions from logical to client and confirmed:

{:list=>true}

"/v1/secrets%2Dkv"

#<URI::HTTPS https://websitehere/v1/secrets%2Dkv?list=true>```

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions