When to use
- User wants to create a new project for deploying use cases
- Before deploying if no project exists for the use case folder
- When
project.jsonis missing and deployment requires a project ID
Prerequisites
codikaCLI installed and authenticated- Valid API key with appropriate scopes
Command
Options
| Option | Required | Description | Default |
|---|---|---|---|
--name <name> | Yes | Project display name | — |
--description <description> | No | Project description | — |
--template-id <id> | No | Template ID for project setup | Platform default |
--organization-id <id> | Admin keys only | Specify target organization | — |
--path <dir> | Recommended | Write project.json to this directory | — |
--project-file <path> | No | Custom filename for project file | project.json |
--api-url <url> | No | Override API URL | — |
--api-key <key> | No | Override API key | — |
--profile <name> | No | Use a specific profile instead of the active one | — |
--json | No | JSON output | — |
Behavior
- Calls the Codika platform API to create the project
- Creates a project in the specified (or inferred) organization
- If
--pathis provided, writesproject.jsoncontainingprojectIdandorganizationId
Recommended usage
Always use--path . when creating a project for a use case folder:
project.json:
project.json:
- Enables org-aware profile selection during deployment
- Auto-resolves
processInstanceIdfor trigger and get commands - Stores
devProcessInstanceIdafter first deploy - Stores
prodProcessInstanceIdafter first publish
Examples
Output
Exit codes
| Code | Meaning |
|---|---|
0 | Success |
1 | API error (auth, network, server) |
2 | CLI validation error (e.g., missing --name) |