phala-network/Phala Cloud CVM Deployment
Deploy a CVM to Phala Cloud using phala.toml configuration
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 27, 2026
- License
- None
Pinned Snippet
uses: phala-network/phala-deploy-action@b6bcce6a26203fcc2fa715a49c09080e46a98927 # v2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| api-key | Phala Cloud API Key. Optional when OIDC is enabled (permissions: id-token: write) | no | "" |
| envs | Environment variables (KEY=VALUE per line) from GitHub Secrets | no | "" |
| cli-version | Phala CLI version to install | no | 1.1.19 |
Outputs
| name | description |
|---|---|
| result | Full CVM info as JSON |
| status | Deployment status (success/failed/pending_approval) |
| app-id | App ID of the deployed CVM |
| vm-uuid | VM UUID of the deployed CVM |
| cvm-name | Name of the deployed CVM |
| dashboard-url | URL to the CVM dashboard |
| compose-hash | Normalized app-compose SHA256 hash |
| docker-compose-hash | Raw docker-compose.yml SHA256 hash |
| pre-launch-script-hash | Pre-launch script SHA256 hash |
| os-image | OS image name |
| os-image-version | OS image version |
| os-image-hash | OS image hash |
| kms-type | Key management type (phala/ethereum/base) |
| device-id | Device ID from node info |
| oidc-repository | Source repository from OIDC verification |
| oidc-commit-sha | Source commit SHA from OIDC verification |
| commit-token | Commit token for 2-step deployment (on-chain KMS) |