chore: remove unused count type from entity query type param

SpecterOps · Oct 4, 2024 · 711c15e · 711c15e
1 parent e37d3ca
commit 711c15e
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/packages/go/openapi/src/parameters/query.entity.type.yaml b/packages/go/openapi/src/parameters/query.entity.type.yaml
@@ -17,14 +17,14 @@
 name: type
 description: |
   The type of return data requested. If no type is provided, query will default to `list`.
-  The only supported type is `list`, but unsupported `graph` and `count` can be used.
-  An invalid type will result in a `count` query. Some entity query endpoints do not
-  support the `graph` type.
+  The only supported type is `list`, but the unsupported `graph` type can be used.
+  Some entity query endpoints do not support the `graph` type. For those interested in
+  using the undocumented graph type parameter, the response type is described in the schema
+  `model.bh-graph.graph`.
 in: query
 schema:
   type: string
   default: list
   enum:
     - list
     - graph
-    - count
diff --git a/packages/go/openapi/src/responses/related-entity-query-results.yaml b/packages/go/openapi/src/responses/related-entity-query-results.yaml
@@ -19,10 +19,10 @@ description: |
 
   This endpoint returns a response, dependent upon which return type is requested by the `type` parameter.
   The only supported `type` parameter is `list`.
-  While `list` is the only supported `type` parameter, the `count` or `graph` parameters can be used
+  While `list` is the only supported `type` parameter, the `graph` parameter can be used
   and will result in a different response structure then documented here.
   For those interested in using the undocumented graph type parameter, the response type is described in the schema
-  model.bh-graph.graph.
+  `model.bh-graph.graph`.
 content:
   application/json:
     schema: