stepzen 0.58.0-experimental.a42e35b → 0.58.0-experimental.a56f2f6

package/README.md

@@ -36,7 +36,7 @@ $ npm install -g stepzen
 $ stepzen COMMAND
 running command...
 $ stepzen (--version|-v)
-stepzen/0.58.0-experimental.a42e35b linux-x64 node-v22.22.2
+stepzen/0.58.0-experimental.a56f2f6 linux-x64 node-v22.22.2
 $ stepzen --help [COMMAND]
 USAGE
   $ stepzen COMMAND
@@ -51,112 +51,8 @@ To run from code: `path-to-repo/bin/run start` (start or whatever command you're
 
 # Commands
 <!-- commands -->
-* [`stepzen delete ENDPOINT`](#stepzen-delete-endpoint)
-* [`stepzen deploy [ENDPOINT] [--config=path/to/config.yaml] [--dir=path/to/workspace]
-
--- OR (deprecated) --
-
-$ stepzen deploy ENDPOINT --schema=schema [--configurationsets=cs1[,cs2[,..]]]`](#stepzen-deploy-endpoint---configpathtoconfigyaml---dirpathtoworkspace---or-deprecated----stepzen-deploy-endpoint---schemaschema---configurationsetscs1cs2)
 * [`stepzen help [COMMAND]`](#stepzen-help-command)
-* [`stepzen import [SOURCE]`](#stepzen-import-source)
-* [`stepzen import curl`](#stepzen-import-curl)
-* [`stepzen import db2 [JDBCURL]`](#stepzen-import-db2-jdbcurl)
-* [`stepzen import flow [FLOW]`](#stepzen-import-flow-flow)
-* [`stepzen import graphql [URL]`](#stepzen-import-graphql-url)
-* [`stepzen import mysql [DSN]`](#stepzen-import-mysql-dsn)
-* [`stepzen import oracle [JDBCURL]`](#stepzen-import-oracle-jdbcurl)
-* [`stepzen import postgres [DSN]`](#stepzen-import-postgres-dsn)
-* [`stepzen import postgresql [DSN]`](#stepzen-import-postgresql-dsn)
-* [`stepzen import singlestore [DSN]`](#stepzen-import-singlestore-dsn)
-* [`stepzen import snowflake [DSN]`](#stepzen-import-snowflake-dsn)
-* [`stepzen init`](#stepzen-init)
-* [`stepzen list [TYPE]`](#stepzen-list-type)
-* [`stepzen login [DOMAIN]`](#stepzen-login-domain)
-* [`stepzen logout`](#stepzen-logout)
-* [`stepzen request [QUERY]`](#stepzen-request-query)
-* [`stepzen service [ACTION]`](#stepzen-service-action)
-* [`stepzen start`](#stepzen-start)
 * [`stepzen version`](#stepzen-version)
-* [`stepzen whoami`](#stepzen-whoami)
-
-## `stepzen delete ENDPOINT`
-
-Delete an endpoint from your StepZen account.
-
-```
-USAGE
-  $ stepzen delete ENDPOINT [-h] [--non-interactive]
-
-ARGUMENTS
-  ENDPOINT  name of the endpoint (e.g. api/customers)
-
-FLAGS
-  -h, --help             Show CLI help
-      --non-interactive  Disable all interactive prompts
-
-DESCRIPTION
-  Delete an endpoint from your StepZen account.
-```
-
-## `stepzen deploy [ENDPOINT] [--config=path/to/config.yaml] [--dir=path/to/workspace]
-
--- OR (deprecated) --
-
-$ stepzen deploy ENDPOINT --schema=schema [--configurationsets=cs1[,cs2[,..]]]`
-
-Deploy to StepZen.
-
-```
-USAGE
-  $ stepzen deploy [ENDPOINT] [--config=path/to/config.yaml] [--dir=path/to/workspace]
-
-  -- OR (deprecated)
-    --
-
-    $ stepzen deploy ENDPOINT --schema=schema [--configurationsets=cs1[,cs2[,..]]]
-
-ARGUMENTS
-  [ENDPOINT]  name of the endpoint (e.g. api/customers)
-              [default: use the endpoint property from stepzen.config.json]
-
-FLAGS
-  -h, --help
-      Show CLI help
-
-  --config=path/to/config.yaml
-      [default: config.yaml] Configuration file to use (relative to the current directory)
-
-  --configurationsets=<value>
-      Name(s) of configuration sets uploaded earlier with stepzen upload
-      [DEPRECATED: this flag will be removed in future versions]
-
-      Instead, please use one of these options:
-      - stepzen deploy (without the --configurationsets flag)
-      to use the configuration from the config.yaml file in the current directory (if exists)
-      - stepzen deploy --config path/to/config.yaml
-      to explicitly specify the configuration file
-
-  --dir=<value>
-      Working directory
-
-  --non-interactive
-      Disable all interactive prompts
-
-  --schema=<value>
-      Name of a schema uploaded earlier with stepzen upload
-      [DEPRECATED: this flag will be removed in future versions]
-
-      Instead, please use one of these options:
-      - stepzen deploy (without the --schema flag)
-      to deploy the schema from a StepZen workspace in your current directory
-      - stepzen deploy --dir path/to/workspace
-      to deploy from a StepZen workspace in another folder
-
-  --silent
-
-DESCRIPTION
-  Deploy to StepZen.
-```
 
 ## `stepzen help [COMMAND]`
 
@@ -178,954 +74,6 @@ DESCRIPTION
 
 _See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/6.2.43/src/commands/help.ts)_
 
-## `stepzen import [SOURCE]`
-
-Import a schema for an external data source or an API endpoint into your GraphQL API.
-
-```
-USAGE
-  $ stepzen import [SOURCE...] [-h] [--non-interactive] [--dir <value>]
-
-ARGUMENTS
-  [SOURCE...]  kind of the data source: curl, graphql, mysql, postgresql, snowflake, db2, oracle (or a full DSN string)
-
-FLAGS
-  -h, --help             Show CLI help
-      --dir=<value>      Working directory
-      --non-interactive  Disable all interactive prompts
-
-DESCRIPTION
-  Import a schema for an external data source or an API endpoint into your GraphQL API.
-  See more details with stepzen import [SOURCE] --help
-```
-
-## `stepzen import curl`
-
-Import a schema for a REST endpoint into your GraphQL API (uses the curl syntax).
-
-```
-USAGE
-  $ stepzen import curl [-h] [--non-interactive] [--dir <value>] [--name <value>] [--prefix <value>] [-H
-    <value>...] [--header-param <value>...] [--query-name <value>] [--query-type <value>] [--path-params <value>]
-    [--secrets <value>...]
-
-FLAGS
-  -H, --header=<value>...
-      Specifies a request header to pass
-
-      Example:
-      stepzen import curl https://example.com/api/customers \
-      -H "Authorization: apikey SecretAPIKeyValue"
-
-  -h, --help
-      Show CLI help
-
-  --dir=<value>
-      Working directory
-
-  --header-param=<value>...
-      Specifies a parameter in a header value. Can be formed by taking a -H, --header flag and replacing the variable part
-      of the header value with a $paramName placeholder. Repeat this flag once for each header with a parameter.
-
-      Example:
-      stepzen import curl https://example.com/api/customers \
-      -H "Authorization: apikey SecretAPIKeyValue" \
-      --header-param 'Authorization: apikey $apikey'
-
-  --name=<value>
-      Subfolder inside the workspace folder to save the imported schema files to. Defaults to the name of the imported
-      schema.
-
-  --non-interactive
-      Disable all interactive prompts
-
-  --path-params=<value>
-      Specifies path parameters in the URL path. Can be formed by taking the original path and replacing the variable
-      segments with $paramName placeholders.
-
-      Example:
-      stepzen import curl https://example.com/users/jane/posts/12 --path-params '/users/$userId/posts/$postId'
-
-  --prefix=<value>
-      Prefix to add to every type in the generated schema
-
-  --query-name=<value>
-      Property name to add to the Query type as a way to access the imported endpoint
-
-  --query-type=<value>
-      Name for the type returned by the curl request in the generated schema. The name specified by --query-type is not
-      prefixed by --prefix if both flags are present.
-
-  --secrets=<value>...
-      Specifies the names of HTTP headers whose values are considered secrets.
-      A header's value is replaced with an expansion variable which is set in config.yaml
-
-      Example:
-      stepzen import curl https://stepzen.us-east-a.ibm.stepzen.net/version \
-      --header 'Authorization: <sensitive value>' \
-      --secrets 'Authorization'
-
-      This ensures that sensitive values are securely stored in generated config.yaml
-
-      ### Example config.yaml outputs:
-      ```yaml
-      configurationset:
-      - configuration:
-      authorization_416efbc0dc: Apikey <sensitive value>
-      name: curl_import_config
-      ```
-
-      In this case, index.graphql must reference "$authorization_416efbc0dc;".
-
-      **headers: [{ name: "authorization", value: "$authorization_416efbc0dc;" }]
-
-DESCRIPTION
-  Import a schema for a REST endpoint into your GraphQL API (uses the curl syntax).
-
-  stepzen import curl automatically introspects a REST endpoint, generates a GraphQL schema for accessing this endpoint
-  through a StepZen API, and adds the generated types and a query field into your GraphQL schema.
-```
-
-## `stepzen import db2 [JDBCURL]`
-
-Import a schema for a Db2 data source into your GraphQL API.
-
-```
-USAGE
-  $ stepzen import db2 [JDBCURL] [-h] [--non-interactive] [--dir <value>] [--name <value>] [--db-schema <value>]
-    [--db-link-types] [--db-include tables-only|views-only|tables-and-views] [--db-use-deprecated-2022-naming]
-
-ARGUMENTS
-  [JDBCURL]  (optional) JDBC URL of a Db2 database.
-             Example: 'jdbc:db2://host:port/db:user=username;password=password;schema=schema;sslConnection=true/false;'
-
-             The --db-schema flag overrides the schema part of the JDBC URL (if both are provided).
-
-FLAGS
-  -h, --help
-      Show CLI help
-
-  --db-include=<option>
-      Should the generated GraphQL schema be based only on database views, only on tables or on both
-      <options: tables-only|views-only|tables-and-views>
-
-  --db-link-types
-      Automatically link types based on foreign key relationships using @materializer
-      (https://stepzen.com/docs/features/linking-types)
-
-  --db-schema=<value>
-      Database schema to import tables from (default: public)
-
-  --db-use-deprecated-2022-naming
-      Use the deprecated pre-2023 naming convention in the generated GraphQL schema:
-      - the generated type and property names are auto-capitalized into PascalCase
-      - the generated field names use the getCustomer and getCustomerList style.
-
-      On the other hand, when using the default naming convention:
-      - the generated type and property names match exactly the DB table and column names
-      - the generated field names use the customer and customerList style.
-
-  --dir=<value>
-      Working directory
-
-  --name=<value>
-      Subfolder inside the workspace folder to save the imported schema files to. Defaults to the name of the imported
-      schema.
-
-  --non-interactive
-      Disable all interactive prompts
-
-DESCRIPTION
-  Import a schema for a Db2 data source into your GraphQL API.
-
-  stepzen import db2 automatically introspects a Db2 database, generates a GraphQL schema for accessing this database
-  through a StepZen API, and merges the generated types, queries and mutations into your GraphQL schema.
-```
-
-## `stepzen import flow [FLOW]`
-
-Import StepZen flow expression as a query field into your GraphQL API.
-
-```
-USAGE
-  $ stepzen import flow [FLOW] [-h] [--non-interactive] [--dir <value>] [--name <value>] [-H <value>...
-    --endpoint <value>]
-
-FLAGS
-  -H, --header=<value>...  Specifies a request header to pass
-
-                           Example:
-                           stepzen import curl https://example.com/api/customers \
-                           -H "Authorization: apikey SecretAPIKeyValue"
-  -h, --help               Show CLI help
-      --dir=<value>        Working directory
-      --endpoint=<value>   Use a custom GraphQL schema instead of the project's schema as the schema providing the steps
-                           in the flow.
-      --name=<value>       Subfolder inside the workspace folder to save the imported schema files to. Defaults to the
-                           name of the imported schema.
-      --non-interactive    Disable all interactive prompts
-
-DESCRIPTION
-  Import StepZen flow expression as a query field into your GraphQL API.
-
-  stepzen import flow automatically introspects a GraphQL endpoint and adds a @sequence implementing the given flow
-  expression into your GraphQL schema.
-```
-
-## `stepzen import graphql [URL]`
-
-Import a GraphQL API as a subgraph into your GraphQL API.
-
-```
-USAGE
-  $ stepzen import graphql [URL] [-h] [--non-interactive] [--dir <value>] [--name <value>] [--prefix <value>] [-H
-    <value>...] [--header-param <value>...] [--secrets <value>...]
-
-FLAGS
-  -H, --header=<value>...
-      Specifies a request header to pass
-
-      Example:
-      stepzen import curl https://example.com/api/customers \
-      -H "Authorization: apikey SecretAPIKeyValue"
-
-  -h, --help
-      Show CLI help
-
-  --dir=<value>
-      Working directory
-
-  --header-param=<value>...
-      Specifies a parameter in a header value. Can be formed by taking a -H, --header flag and replacing the variable part
-      of the header value with a $paramName placeholder. Repeat this flag once for each header with a parameter.
-
-      Example:
-      stepzen import curl https://example.com/api/customers \
-      -H "Authorization: apikey SecretAPIKeyValue" \
-      --header-param 'Authorization: apikey $apikey'
-
-  --name=<value>
-      Subfolder inside the workspace folder to save the imported schema files to. Defaults to the name of the imported
-      schema.
-
-  --non-interactive
-      Disable all interactive prompts
-
-  --prefix=<value>
-      Prefix to add to every type in the generated schema
-
-  --secrets=<value>...
-      Specifies the names of HTTP headers whose values are considered secrets.
-      A header's value is replaced with an expansion variable which is set in config.yaml
-
-      Example:
-      stepzen import curl https://stepzen.us-east-a.ibm.stepzen.net/version \
-      --header 'Authorization: <sensitive value>' \
-      --secrets 'Authorization'
-
-      This ensures that sensitive values are securely stored in generated config.yaml
-
-      ### Example config.yaml outputs:
-      ```yaml
-      configurationset:
-      - configuration:
-      authorization_416efbc0dc: Apikey <sensitive value>
-      name: curl_import_config
-      ```
-
-      In this case, index.graphql must reference "$authorization_416efbc0dc;".
-
-      **headers: [{ name: "authorization", value: "$authorization_416efbc0dc;" }]
-
-DESCRIPTION
-  Import a GraphQL API as a subgraph into your GraphQL API.
-
-  stepzen import graphql automatically introspects a GraphQL endpoint and merges the types, queries, mutations and
-  subscriptions for accessing this endpoint through a StepZen API into your GraphQL schema.
-```
-
-## `stepzen import mysql [DSN]`
-
-Import a schema for a MySQL data source into your GraphQL API.
-
-```
-USAGE
-  $ stepzen import mysql [DSN] [-h] [--non-interactive] [--dir <value>] [--name <value>] [--db-host <value>]
-    [--db-user <value>] [--db-password <value>] [--db-database <value>] [--db-link-types] [--db-include
-    tables-only|views-only|tables-and-views] [--db-use-deprecated-2022-naming]
-
-ARGUMENTS
-  [DSN]  (optional) Data Source Name (DSN) of a MySQL database.
-         Example: mysql://user:password@host:port/database
-
-         Flags, such as --db-host, override the corresponding parts of the DSN (if both are provided).
-
-FLAGS
-  -h, --help
-      Show CLI help
-
-  --db-database=<value>
-      Name of database to import
-
-  --db-host=<value>
-      Database host and optional port (as HOST[:PORT])
-
-  --db-include=<option>
-      Should the generated GraphQL schema be based only on database views, only on tables or on both
-      <options: tables-only|views-only|tables-and-views>
-
-  --db-link-types
-      Automatically link types based on foreign key relationships using @materializer
-      (https://stepzen.com/docs/features/linking-types)
-
-  --db-password=<value>
-      Database password
-
-  --db-use-deprecated-2022-naming
-      Use the deprecated pre-2023 naming convention in the generated GraphQL schema:
-      - the generated type and property names are auto-capitalized into PascalCase
-      - the generated field names use the getCustomer and getCustomerList style.
-
-      On the other hand, when using the default naming convention:
-      - the generated type and property names match exactly the DB table and column names
-      - the generated field names use the customer and customerList style.
-
-  --db-user=<value>
-      Database user name
-
-  --dir=<value>
-      Working directory
-
-  --name=<value>
-      Subfolder inside the workspace folder to save the imported schema files to. Defaults to the name of the imported
-      schema.
-
-  --non-interactive
-      Disable all interactive prompts
-
-DESCRIPTION
-  Import a schema for a MySQL data source into your GraphQL API.
-
-  stepzen import mysql automatically introspects a MySQL database, generates a GraphQL schema for accessing this
-  database through a StepZen API, and merges the generated types, queries and mutations into your into your GraphQL
-  schema.
-
-ALIASES
-  $ stepzen import singlestore
-```
-
-## `stepzen import oracle [JDBCURL]`
-
-Import a schema for a oracle data source into your GraphQL API.
-
-```
-USAGE
-  $ stepzen import oracle [JDBCURL] [-h] [--non-interactive] [--dir <value>] [--name <value>] [--db-schema <value>]
-    [--db-link-types] [--db-include tables-only|views-only|tables-and-views] [--db-use-deprecated-2022-naming]
-
-ARGUMENTS
-  [JDBCURL]  (optional) JDBC URL of an Oracle database.
-             Example: 'jdbc:oracle:thin:user/password@//host:port/db?currentschema=schema'
-
-             The --db-schema flag overrides the schema part of the JDBC URL (if both are provided).
-
-FLAGS
-  -h, --help
-      Show CLI help
-
-  --db-include=<option>
-      Should the generated GraphQL schema be based only on database views, only on tables or on both
-      <options: tables-only|views-only|tables-and-views>
-
-  --db-link-types
-      Automatically link types based on foreign key relationships using @materializer
-      (https://stepzen.com/docs/features/linking-types)
-
-  --db-schema=<value>
-      Database schema to import tables from (default: public)
-
-  --db-use-deprecated-2022-naming
-      Use the deprecated pre-2023 naming convention in the generated GraphQL schema:
-      - the generated type and property names are auto-capitalized into PascalCase
-      - the generated field names use the getCustomer and getCustomerList style.
-
-      On the other hand, when using the default naming convention:
-      - the generated type and property names match exactly the DB table and column names
-      - the generated field names use the customer and customerList style.
-
-  --dir=<value>
-      Working directory
-
-  --name=<value>
-      Subfolder inside the workspace folder to save the imported schema files to. Defaults to the name of the imported
-      schema.
-
-  --non-interactive
-      Disable all interactive prompts
-
-DESCRIPTION
-  Import a schema for a oracle data source into your GraphQL API.
-
-  stepzen import oracle automatically introspects an Oracle database, generates a GraphQL schema for accessing this
-  database through a StepZen API, and merges the generated types, queries and mutations into your GraphQL schema.
-```
-
-## `stepzen import postgres [DSN]`
-
-Import a schema for a PostgreSQL data source into your GraphQL API.
-
-```
-USAGE
-  $ stepzen import postgres [DSN] [-h] [--non-interactive] [--dir <value>] [--name <value>] [--db-host <value>]
-    [--db-user <value>] [--db-password <value>] [--db-database <value>] [--db-schema <value>] [--db-link-types]
-    [--db-include tables-only|views-only|tables-and-views] [--db-use-deprecated-2022-naming]
-
-ARGUMENTS
-  [DSN]  (optional) Data Source Name (DSN) of a PostgreSQL database.
-         Example: postgresql://user:password@host:port/database?schema=schema
-
-         Flags, such as --db-host, override the corresponding parts of the DSN (if both are provided).
-
-FLAGS
-  -h, --help
-      Show CLI help
-
-  --db-database=<value>
-      Name of database to import
-
-  --db-host=<value>
-      Database host and optional port (as HOST[:PORT])
-
-  --db-include=<option>
-      Should the generated GraphQL schema be based only on database views, only on tables or on both
-      <options: tables-only|views-only|tables-and-views>
-
-  --db-link-types
-      Automatically link types based on foreign key relationships using @materializer
-      (https://stepzen.com/docs/features/linking-types)
-
-  --db-password=<value>
-      Database password
-
-  --db-schema=<value>
-      Database schema to import tables from (default: public)
-
-  --db-use-deprecated-2022-naming
-      Use the deprecated pre-2023 naming convention in the generated GraphQL schema:
-      - the generated type and property names are auto-capitalized into PascalCase
-      - the generated field names use the getCustomer and getCustomerList style.
-
-      On the other hand, when using the default naming convention:
-      - the generated type and property names match exactly the DB table and column names
-      - the generated field names use the customer and customerList style.
-
-  --db-user=<value>
-      Database user name
-
-  --dir=<value>
-      Working directory
-
-  --name=<value>
-      Subfolder inside the workspace folder to save the imported schema files to. Defaults to the name of the imported
-      schema.
-
-  --non-interactive
-      Disable all interactive prompts
-
-DESCRIPTION
-  Import a schema for a PostgreSQL data source into your GraphQL API.
-
-  stepzen import postgresql automatically introspects a PostgreSQL database, generates a GraphQL schema for accessing
-  this database through a StepZen API, and merges the generated types, queries and mutations into your GraphQL schema.
-
-ALIASES
-  $ stepzen import postgres
-```
-
-## `stepzen import postgresql [DSN]`
-
-Import a schema for a PostgreSQL data source into your GraphQL API.
-
-```
-USAGE
-  $ stepzen import postgresql [DSN] [-h] [--non-interactive] [--dir <value>] [--name <value>] [--db-host <value>]
-    [--db-user <value>] [--db-password <value>] [--db-database <value>] [--db-schema <value>] [--db-link-types]
-    [--db-include tables-only|views-only|tables-and-views] [--db-use-deprecated-2022-naming]
-
-ARGUMENTS
-  [DSN]  (optional) Data Source Name (DSN) of a PostgreSQL database.
-         Example: postgresql://user:password@host:port/database?schema=schema
-
-         Flags, such as --db-host, override the corresponding parts of the DSN (if both are provided).
-
-FLAGS
-  -h, --help
-      Show CLI help
-
-  --db-database=<value>
-      Name of database to import
-
-  --db-host=<value>
-      Database host and optional port (as HOST[:PORT])
-
-  --db-include=<option>
-      Should the generated GraphQL schema be based only on database views, only on tables or on both
-      <options: tables-only|views-only|tables-and-views>
-
-  --db-link-types
-      Automatically link types based on foreign key relationships using @materializer
-      (https://stepzen.com/docs/features/linking-types)
-
-  --db-password=<value>
-      Database password
-
-  --db-schema=<value>
-      Database schema to import tables from (default: public)
-
-  --db-use-deprecated-2022-naming
-      Use the deprecated pre-2023 naming convention in the generated GraphQL schema:
-      - the generated type and property names are auto-capitalized into PascalCase
-      - the generated field names use the getCustomer and getCustomerList style.
-
-      On the other hand, when using the default naming convention:
-      - the generated type and property names match exactly the DB table and column names
-      - the generated field names use the customer and customerList style.
-
-  --db-user=<value>
-      Database user name
-
-  --dir=<value>
-      Working directory
-
-  --name=<value>
-      Subfolder inside the workspace folder to save the imported schema files to. Defaults to the name of the imported
-      schema.
-
-  --non-interactive
-      Disable all interactive prompts
-
-DESCRIPTION
-  Import a schema for a PostgreSQL data source into your GraphQL API.
-
-  stepzen import postgresql automatically introspects a PostgreSQL database, generates a GraphQL schema for accessing
-  this database through a StepZen API, and merges the generated types, queries and mutations into your GraphQL schema.
-
-ALIASES
-  $ stepzen import postgres
-```
-
-## `stepzen import singlestore [DSN]`
-
-Import a schema for a MySQL data source into your GraphQL API.
-
-```
-USAGE
-  $ stepzen import singlestore [DSN] [-h] [--non-interactive] [--dir <value>] [--name <value>] [--db-host <value>]
-    [--db-user <value>] [--db-password <value>] [--db-database <value>] [--db-link-types] [--db-include
-    tables-only|views-only|tables-and-views] [--db-use-deprecated-2022-naming]
-
-ARGUMENTS
-  [DSN]  (optional) Data Source Name (DSN) of a MySQL database.
-         Example: mysql://user:password@host:port/database
-
-         Flags, such as --db-host, override the corresponding parts of the DSN (if both are provided).
-
-FLAGS
-  -h, --help
-      Show CLI help
-
-  --db-database=<value>
-      Name of database to import
-
-  --db-host=<value>
-      Database host and optional port (as HOST[:PORT])
-
-  --db-include=<option>
-      Should the generated GraphQL schema be based only on database views, only on tables or on both
-      <options: tables-only|views-only|tables-and-views>
-
-  --db-link-types
-      Automatically link types based on foreign key relationships using @materializer
-      (https://stepzen.com/docs/features/linking-types)
-
-  --db-password=<value>
-      Database password
-
-  --db-use-deprecated-2022-naming
-      Use the deprecated pre-2023 naming convention in the generated GraphQL schema:
-      - the generated type and property names are auto-capitalized into PascalCase
-      - the generated field names use the getCustomer and getCustomerList style.
-
-      On the other hand, when using the default naming convention:
-      - the generated type and property names match exactly the DB table and column names
-      - the generated field names use the customer and customerList style.
-
-  --db-user=<value>
-      Database user name
-
-  --dir=<value>
-      Working directory
-
-  --name=<value>
-      Subfolder inside the workspace folder to save the imported schema files to. Defaults to the name of the imported
-      schema.
-
-  --non-interactive
-      Disable all interactive prompts
-
-DESCRIPTION
-  Import a schema for a MySQL data source into your GraphQL API.
-
-  stepzen import mysql automatically introspects a MySQL database, generates a GraphQL schema for accessing this
-  database through a StepZen API, and merges the generated types, queries and mutations into your into your GraphQL
-  schema.
-
-ALIASES
-  $ stepzen import singlestore
-```
-
-## `stepzen import snowflake [DSN]`
-
-Import a schema for a Snowflake data source into your GraphQL API.
-
-```
-USAGE
-  $ stepzen import snowflake [DSN] [-h] [--non-interactive] [--dir <value>] [--name <value>] [--db-user <value>]
-    [--db-password <value>] [--db-database <value>] [--db-schema <value>] [--db-link-types] [--db-include
-    tables-only|views-only|tables-and-views] [--db-use-deprecated-2022-naming] [--snowflake-account-id <value>]
-    [--snowflake-warehouse <value>]
-
-ARGUMENTS
-  [DSN]  (optional) Data Source Name (DSN) of a Snowflake database.
-         Example: snowflake://user:password@orgname-accountname/database?warehouse=warehouse&schema=schema
-
-         Flags, such as --db-host, override the corresponding parts of the DSN (if both are provided).
-
-FLAGS
-  -h, --help
-      Show CLI help
-
-  --db-database=<value>
-      Name of database to import
-
-  --db-include=<option>
-      Should the generated GraphQL schema be based only on database views, only on tables or on both
-      <options: tables-only|views-only|tables-and-views>
-
-  --db-link-types
-      Automatically link types based on foreign key relationships using @materializer
-      (https://stepzen.com/docs/features/linking-types)
-
-  --db-password=<value>
-      Database password
-
-  --db-schema=<value>
-      Database schema to import tables from (default: PUBLIC)
-
-  --db-use-deprecated-2022-naming
-      Use the deprecated pre-2023 naming convention in the generated GraphQL schema:
-      - the generated type and property names are auto-capitalized into PascalCase
-      - the generated field names use the getCustomer and getCustomerList style.
-
-      On the other hand, when using the default naming convention:
-      - the generated type and property names match exactly the DB table and column names
-      - the generated field names use the customer and customerList style.
-
-  --db-user=<value>
-      Database user name
-
-  --dir=<value>
-      Working directory
-
-  --name=<value>
-      Subfolder inside the workspace folder to save the imported schema files to. Defaults to the name of the imported
-      schema.
-
-  --non-interactive
-      Disable all interactive prompts
-
-  --snowflake-account-id=<value>
-      Snowflake account identifier in the orgname-accountname format. For more information, see the Snowflake
-      documentation at https://docs.snowflake.com/en/user-guide/admin-account-identifier.html.
-
-  --snowflake-warehouse=<value>
-      Snowflake warehouse
-
-DESCRIPTION
-  Import a schema for a Snowflake data source into your GraphQL API.
-
-  stepzen import snowflake automatically introspects a Snowflake database, generates a GraphQL schema for accessing this
-  database through a StepZen API, and merges the generated types, queries and mutations into your GraphQL schema.
-```
-
-## `stepzen init`
-
-Initialize a StepZen workspace in the current directory.
-
-```
-USAGE
-  $ stepzen init [-h] [--non-interactive] [--endpoint <value>] [--yes]
-
-FLAGS
-  -h, --help              Show CLI help
-      --endpoint=<value>  Endpoint name (e.g. api/myapp)
-      --non-interactive   Disable all interactive prompts
-      --yes               Accept default answers to interactive prompts
-
-DESCRIPTION
-  Initialize a StepZen workspace in the current directory.
-```
-
-## `stepzen list [TYPE]`
-
-List endpoints, schemas and configuration sets in your StepZen account.
-
-```
-USAGE
-  $ stepzen list [TYPE] [-h] [--non-interactive] [--folder <value>] [--name <value>]
-
-ARGUMENTS
-  [TYPE]  [default: endpoints]
-
-          The type of entities to list:
-          endpoints - GraphQL API endpoints deployed with stepzen deploy (or stepzen start)
-
-FLAGS
-  -h, --help             Show CLI help
-      --folder=<value>   Filter the list to only show endpoints within a specific folder. example usage --folder
-                         folder_name or --folder !folder_name
-      --name=<value>     Filter the list to only show endpoints with a specific name. example usage --name endpoint_name
-                         or --name '!endpoint_name'
-      --non-interactive  Disable all interactive prompts
-
-DESCRIPTION
-  List endpoints, schemas and configuration sets in your StepZen account.
-  All timestamps displayed by stepzen list endpoints are in your local time zone.
-```
-
-## `stepzen login [DOMAIN]`
-
-Log in to StepZen.
-
-```
-USAGE
-  $ stepzen login [DOMAIN] [-h] [--non-interactive] [-a <value> | ] [-k <value> | ] [--introspection
-    <value>] [-i <value>]
-
-ARGUMENTS
-  [DOMAIN]  Domain of the StepZen service to login to (e.g. us-east-a.ibm.stepzen.net or eu-central-a.ibm.stepzen.net).
-            If no domain is provided, stepzen.net is used by default. Check you domain from the StepZen Dashboard.
-
-FLAGS
-  -a, --account=<value>        StepZen account name (copy from https://stepzen.com/account). If not provided, the CLI
-                               prompts the users to enter one.
-  -h, --help                   Show CLI help
-  -i, --instanceId=<value>     Instance ID of your subscribed StepZen instance. You can find this in the SaaS console
-                               under Subscriptions → APIConnect for GraphQL → Instances.
-  -k, --adminkey=<value>       Key used for authentication. If used with `-i <instance_id>`, it is treated as the API
-                               key for the instance (get it from https://aws.console.saas.ibm.com/ under "API Keys"). If
-                               used with `-a <account>`, it is treated as the Admin key (get it from the dashbaord
-                               https://dashboard.ibm.stepzen.com/) ). If not provided, the CLI will prompt for it.
-      --introspection=<value>  Override the default StepZen introspection service URL for all stepzen import commands.
-                               If not provided, use the default introspection URL.
-
-                               Example:
-                               stepzen login --introspection stepzen-introspection.mydomain.com
-      --non-interactive        Disable all interactive prompts
-
-DESCRIPTION
-  Log in to StepZen.
-```
-
-## `stepzen logout`
-
-Log out of StepZen.
-
-```
-USAGE
-  $ stepzen logout [-h] [--non-interactive]
-
-FLAGS
-  -h, --help             Show CLI help
-      --non-interactive  Disable all interactive prompts
-
-DESCRIPTION
-  Log out of StepZen.
-```
-
-## `stepzen request [QUERY]`
-
-Send a GraphQL request to a StepZen endpoint and print the response, using the API key and the target endpoint from the current StepZen workspace.
-
-```
-USAGE
-  $ stepzen request [QUERY] [-h] [--non-interactive] [--dir <value> | --endpoint <value>] [-H <value>...]
-    [--operation-name <value>] [--var <value>...] [--var-file <value>] [-f <value>]
-
-ARGUMENTS
-  [QUERY]  GraphQL query (could include a query, a mutation or a subscription).
-           This argument is required unless you provide the query as a file with --file=file.
-
-FLAGS
-  -H, --header=<value>...
-      Add an additional HTTP header to the request. This is useful for schemas where @rest or @graphql directives enable
-      header forwarding with forwardheaders.
-
-      Example:
-      stepzen request '{ user(id: "u123") { email } }' \
-      -H "X-API-Token: SecretAPIToken"
-
-      Use the -H "Header-Name:" syntax to drop a default header, and the -H "Header-Name;" syntax to send a header with an
-      empty value.
-
-  -f, --file=<value>
-      Read the query text from a file instead of the command line.
-
-      Example:
-      stepzen request -f query.graphql
-
-  -h, --help
-      Show CLI help
-
-  --dir=<value>
-      StepZen workspace directory (defaults to the current directory)
-
-  --endpoint=<value>
-      StepZen endpoint to call (defaults to the endpoint in current StepZen workspace)
-
-  --non-interactive
-      Disable all interactive prompts
-
-  --operation-name=<value>
-      Specify the operation name (in case if the provided query includes multiple operations)
-
-  --var=<value>...
-      Add a request variable, in the name=value format.
-
-      Example:
-      stepzen request 'query OrdersQuery($search: String!, $limit: Int) {
-      orders(search: $search, limit: $limit) { id createdAt }
-      }' \
-      --var 'search=space ninja' \
-      --var limit=5
-
-  --var-file=<value>
-      Read request variables from a JSON file. In case when the same variable value is provided both via --var-file and
-      --var, the priority is given to the latter.
-
-      Example:
-      stepzen request 'query OrdersQuery($search: String!, $limit: Int) {
-      orders(search: $search, limit: $limit) { id createdAt }
-      }' \
-      --var-file ./vars.json
-
-DESCRIPTION
-  Send a GraphQL request to a StepZen endpoint and print the response, using the API key and the target endpoint from
-  the current StepZen workspace.
-```
-
-## `stepzen service [ACTION]`
-
-Manage the local StepZen service instance (requires Docker).
-
-```
-USAGE
-  $ stepzen service [ACTION] [-h] [--non-interactive] [--dsn <value> | --reset-auto | --prompt] [--port
-    <value>] [--driver-path <value>...]
-
-ARGUMENTS
-  [ACTION]
-      (start|stop|upgrade)
-      start	start a local StepZen service instance in a Docker container
-      This command pulls the latest StepZen service instance Docker image so that the
-      version of StepZen you run locally is the same as the one running on
-      		stepzen.net.
-
-      stop	stop the local StepZen service instance (if running)
-      This command deletes the Docker container with the StepZen service instance,
-      but all your endpoints are persistently stored in the metadata database. They
-      remain available when running stepzen service start next time.
-
-      upgrade	upgrade the local StepZen service instance if it is running
-      This command checks if a newer version of the StepZen service instance Docker
-      image is available, and if it is then stops and deletes the currently running
-      container, pulls the latest image, and starts it. All endpoints are preserved.
-
-      If no action is provided, print the service status and exit.
-
-FLAGS
-  -h, --help
-      Show CLI help
-
-  --driver-path=<value>...
-      (Optional) Mount a local directory containing additional JDBC drivers to the API Connect Essentials Docker container
-      for the introspection service. This setup is required when JDBC driver licenses restrict the distribution of certain
-      drivers (such as those for Db2 and Oracle) along with the API Connect Essentials Docker image.
-
-      Example: stepzen service start --driver-path "path1" --driver-path "path2"
-
-  --dsn=<value>
-      DSN of a StepZen metadata database, e.g. postgres://user:password@172.17.0.1:5432/zenctl
-
-  --non-interactive
-      Disable all interactive prompts
-
-  --port=<value>
-      Override the TCP port on which the local StepZen service instance will listen for connections (port 9000 by
-      default).
-
-  --prompt
-      Opens an interactive prompt to ask for database details (or fails, if running in a non-interactive mode).
-
-  --reset-auto
-      Create fresh empty metadata database. Note: all existing endpoints will be deleted and you will be logged out.
-
-DESCRIPTION
-  Manage the local StepZen service instance (requires Docker).
-  You can use a local StepZen service instance instead of the StepZen cloud to develop and test GraphQL endpoints
-  locally. This way you can try StepZen out without giving the StepZen cloud access to your data sources and API
-  endpoints.
-
-  Local StepZen service instances are not suitable for production use. Please refer to the documentation at
-  https://stepzen.com/docs/deployment/local-docker for more information and examples.
-```
-
-## `stepzen start`
-
-Deploy your schema to StepZen, and then redeploy on every change.
-
-```
-USAGE
-  $ stepzen start [-h] [--non-interactive] [--dir <value>] [--endpoint <value>] [--dashboard
-    web|local|none] [--port <value>]
-
-FLAGS
-  -h, --help
-      Show CLI help
-
-  --dashboard=<option>
-      Which GraphiQL dashboard to use to explore the deployed endpoint.
-      - web [default]: use GraphiQL at dashboard.stepzen.com
-      - local: start a local GraphiQL dashboard on localhost:5001 (change the port with the --port flag)
-      - none: do not use GraphiQL at all
-      <options: web|local|none>
-
-  --dir=<value>
-      Working directory
-
-  --endpoint=<value>
-      Override workspace endpoint
-
-  --non-interactive
-      Disable all interactive prompts
-
-  --port=<value>
-      [default: 5001, env: PORT] Port for the local GraphiQL dashboard (when using --dashboard=local)
-
-DESCRIPTION
-  Deploy your schema to StepZen, and then redeploy on every change.
-```
-
 ## `stepzen version`
 
 ```
@@ -1145,29 +93,4 @@ FLAG DESCRIPTIONS
 ```
 
 _See code: [@oclif/plugin-version](https://github.com/oclif/plugin-version/blob/2.2.41/src/commands/version.ts)_
-
-## `stepzen whoami`
-
-View your StepZen credentials.
-
-```
-USAGE
-  $ stepzen whoami [-h] [--non-interactive] [--showkeys | --account | --adminkey | --apikey | --domain |
-    --instanceid | --email | --accesstoken]
-
-FLAGS
-  -h, --help             Show CLI help
-  --accesstoken
-  --account
-  --adminkey
-  --apikey
-  --domain
-  --email
-  --instanceid
-      --non-interactive  Disable all interactive prompts
-  --showkeys
-
-DESCRIPTION
-  View your StepZen credentials.
-```
 <!-- commandsstop -->