-
Notifications
You must be signed in to change notification settings - Fork 6
Version Command
Raju Gurram edited this page Dec 20, 2025
·
1 revision
The version command displays version information about the Graphman client, including the client version, schema version, supported schemas, and available extensions.
graphman versionThis command takes no parameters.
The version command displays the following information:
| Information | Description |
|---|---|
| Client Version | The current version of the Graphman client |
| Schema Version | The currently active GraphQL schema version |
| Supported Schemas | List of all supported schema versions |
| Supported Extensions | List of available extension modules |
| Home Directory | Path to the Graphman home directory |
| GitHub Repository | Link to the Graphman GitHub repository |
Display version information:
graphman versionSample Output:
graphman client v2.0.0
schema v11.2.0
supported schema(s) [v11.2.0, v11.1.3, v11.1.2, v11.1.1]
supported extension(s) [pre-request, post-export, pre-import, multiline-text-diff, policy-code-validator]
home /path/to/graphman/home
github https://github.com/...
Check that Graphman is properly installed and accessible:
graphman versionVerify which schema versions are supported before working with a specific Gateway version:
graphman versionInclude version information when reporting issues or seeking support:
graphman version > version-info.txtVerify the Graphman version in automation scripts before executing operations:
#!/bin/bash
graphman version
# ... rest of automation script- The version command requires no configuration or Gateway connectivity
- This is typically the first command to run when setting up or troubleshooting Graphman
- The supported extensions list shows which extension modules are available in your installation
- The home directory path indicates where Graphman looks for configuration files
- config: Configure Graphman home directory and settings
- schema: View and manage GraphQL schema information
The supported extensions may include:
- pre-request: Modify requests before they are sent to the Gateway
- post-export: Process exported data before saving
- pre-import: Process data before importing to the Gateway
- multiline-text-diff: Enhanced diff capabilities for multiline text
- policy-code-validator: Validate policy code syntax and structure