sourceplane/kiox
Install kiox, prepare a workspace, and run commands in the current kiox execution model
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| version | kiox version to install (for example v0.4.2); when omitted or set to latest, the action resolves the latest published kiox release tag | no | — |
| install-url | Override for the kiox installer script URL; when omitted, the action uses install.sh from the resolved kiox tag | no | — |
| workspace | Workspace target to initialize. Accepts either: - Path to an existing kiox workspace manifest file (kind: Workspace) - Workspace directory or name to create | no | — |
| providers | Provider specs to add to a workspace (one per line). When 'workspace' is omitted, the action creates a transient workspace for this step. Format: <source> [as <alias>] [--plain-http] Examples: core/node as node ghcr.io/acme/kubectl:v1.31.0 as kubectl --plain-http | no | — |
| run | Shell commands to execute after setup. kiox is always available on PATH. When a workspace is configured, commands run inside the workspace environment, so provider aliases are available on PATH for this step. | no | — |
| working-directory | Working directory for all kiox operations | no | . |
| outputs | Output file mappings (one per line): name=file_path File contents are set as individual step outputs and aggregated into the outputs-json output. | no | — |
| artifacts | Artifact file paths to upload (one per line) | no | — |
| artifact-name | Name for the uploaded artifact bundle | no | kiox-artifacts |
Outputs
| name | description |
|---|---|
| kiox-version | Installed kiox version string |
| workspace-name | Initialized workspace name |
| workspace-root | Initialized workspace root directory |
| outputs-json | JSON object built from the output file mappings |