# Filters the synced REST API spec (spec/openapi.yml) down to the endpoint
# tags each SDK exposes; everything else (admin, access-tokens, api-keys,
# untagged endpoints like /health) is dropped. The SDK generate pipelines run
# `redocly bundle <api> -o spec/openapi_generated.<api>.yml` before invoking
# their client generators. The js-sdk list additionally keeps `auth` because
# the CLI reaches /teams through the js-sdk's generated schema.
#
# filter-out drops any node (operation or component schema) the upstream
# specs mark `x-not-implemented: true`. It has no applyTo on purpose: the
# flag must work on schemas as well as operations. A kept operation that
# still references a dropped schema loses that media-type entry rather
# than keeping a dangling $ref.
#
# The envd api filters the synced envd spec (spec/envd/envd.yaml) the same
# way: operations the upstream spec marks `x-internal: true` belong to the
# orchestrator's control plane, not to SDKs, so they are dropped before the
# js-sdk envd schema is generated. remove-unused-components then drops the
# component schemas only those operations referenced.
apis:
  js-sdk:
    root: spec/openapi.yml
    decorators:
      filter-in:
        property: tags
        value: [sandboxes, snapshots, templates, tags, auth, volumes, secrets]
        matchStrategy: any
        applyTo: Operation
      filter-out:
        property: x-not-implemented
        value: [true]
  python-sdk:
    root: spec/openapi.yml
    decorators:
      filter-in:
        property: tags
        value: [sandboxes, snapshots, templates, tags, volumes, secrets]
        matchStrategy: any
        applyTo: Operation
      filter-out:
        property: x-not-implemented
        value: [true]
  envd:
    root: spec/envd/envd.yaml
    decorators:
      filter-out:
        property: x-internal
        value: [true]
      remove-unused-components: on