Skip to content

Unable to disable secret engine with dangling creds #122

@Syoc

Description

@Syoc

Running vault secrets disable kubernetes fails here if credentials are issued but the k8s cluster is no longer available.
The consequence seems to be that the secret engine cannot be removed.

There should probably be another function that is used when disabling the secret engine that tries to revoke the secret, but fails more gracefully.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions