Skip to content
Proud to collaborate with Microsoft for Startups

kubernetes.role.delete ​

Delete a namespaced Kubernetes Role (rbac.authorization.k8s.io/v1)

Deletes a namespaced Role (rbac.authorization.k8s.io/v1). Swallows 404 so the workflow is idempotent.

Deleting a Role does not delete the RoleBindings that reference it; those bindings are left dangling and stop granting permissions. Pair this with kubernetes.rolebinding.delete when tearing down a full grant.

Inputs:

  • connection_uuid: Cloud connection UUID (required)
  • namespace: Target namespace (required)
  • name: Role name (required)

Outputs:

  • connection_uuid, namespace, name, existed: bool

Plugin required: context.get_plugin("connection").kubernetes_runner_clients(connection_uuid, organization_uuid) must expose rbac_authorization_v1 (a RbacAuthorizationV1Api instance) with delete_namespaced_role.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-kubernetes
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
connection_uuiduuidYes——
namespacestringYes——
namestringYes——
organization_uuiduuidNo——

Output Schema ​

FieldTypeRequiredDefaultDescription
connection_uuiduuidNo——
organization_uuiduuidNo——
namespacestringNo——
namestringNo——
existedbooleanNo——
failure_reasonstringNo——
failure_typestringNo——
failed_actionstringNo——
failed_at_statestringNo——
failed_stepstringNo——
failed_layerstringNo——
errorstringNo——
error_typestringNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—execute—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "kubernetes.role.delete",
  "initial_data": {
    "connection_uuid": "value",
    "namespace": "value",
    "name": "value"
  }
}