Skip to main content

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.json is missing and deployment requires a project ID

Prerequisites

  • codika CLI installed and authenticated
  • Valid API key with appropriate scopes

Command

Options

Behavior

  1. Calls the Codika platform API to create the project
  2. Creates a project in the specified (or inferred) organization
  3. If --path is provided, writes project.json containing projectId and organizationId
Always use --path . when creating a project for a use case folder:
This writes project.json:
Benefits of project.json:
  • Enables org-aware profile selection during deployment
  • Auto-resolves processInstanceId for trigger and get commands
  • Stores devProcessInstanceId after first deploy
  • Stores prodProcessInstanceId after first publish

Examples

Output

Exit codes