socialweb.computer

Request and provide VMs on an atproto compute market.

lexicons and xrpc

lexicon

com.publicdomainrelay.temp.cluster.revokeKubeconfig

procedure HTTP POST /xrpc/com.publicdomainrelay.temp.cluster.revokeKubeconfig

The gateway revokes one kubeconfig of the named cluster of the calling account: it sets spec.revoked on its ClusterClientCertificate record. The client certificate front admits a certificate only while its record exists and is not revoked, so the kubeconfig stops working within the front's watch latency. Idempotent. deleteCluster, revokeIdentity and signing out of the web app revoke every kubeconfig of a cluster the same way.

input

encoding application/json

fieldtypedescription
name *string
The cluster label of the calling account.
serial *string
The serial from listKubeconfigs.

output

encoding application/json

fieldtypedescription
serial *string
revoked *boolean

errors

errordescription
InvalidRequestName or serial absent.
UnauthorizedMissing or invalid service-auth token.
ClusterNotFoundThis account has no cluster of that name.
KubeconfigNotFoundNo kubeconfig with that serial in this cluster.
ClusterUnavailable503: the gateway could not resolve the token issuer's signing key in time. Retry.
InternalError500: a failure the gateway maps to no named error.

used in

no page of these docs names it yet.

raw schema: lexicons/com/publicdomainrelay/temp/cluster/revokeKubeconfig.json
{
  "lexicon": 1,
  "id": "com.publicdomainrelay.temp.cluster.revokeKubeconfig",
  "defs": {
    "main": {
      "type": "procedure",
      "description": "The gateway revokes one kubeconfig of the named cluster of the calling account: it sets spec.revoked on its ClusterClientCertificate record. The client certificate front admits a certificate only while its record exists and is not revoked, so the kubeconfig stops working within the front's watch latency. Idempotent. deleteCluster, revokeIdentity and signing out of the web app revoke every kubeconfig of a cluster the same way.",
      "input": {
        "encoding": "application/json",
        "schema": {
          "type": "object",
          "required": [
            "name",
            "serial"
          ],
          "properties": {
            "name": {
              "type": "string",
              "description": "The cluster label of the calling account."
            },
            "serial": {
              "type": "string",
              "description": "The serial from listKubeconfigs."
            }
          }
        }
      },
      "output": {
        "encoding": "application/json",
        "schema": {
          "type": "object",
          "required": [
            "serial",
            "revoked"
          ],
          "properties": {
            "serial": {
              "type": "string"
            },
            "revoked": {
              "type": "boolean"
            }
          }
        }
      },
      "errors": [
        {
          "name": "InvalidRequest",
          "description": "Name or serial absent."
        },
        {
          "name": "Unauthorized",
          "description": "Missing or invalid service-auth token."
        },
        {
          "name": "ClusterNotFound",
          "description": "This account has no cluster of that name."
        },
        {
          "name": "KubeconfigNotFound",
          "description": "No kubeconfig with that serial in this cluster."
        },
        {
          "name": "ClusterUnavailable",
          "description": "503: the gateway could not resolve the token issuer's signing key in time. Retry."
        },
        {
          "name": "InternalError",
          "description": "500: a failure the gateway maps to no named error."
        }
      ]
    }
  }
}