Docs

zitadel projects update

Update a project by id.

Usage

npx @zitadel/cli@latest projects update <id> [flags]

Arguments

ArgumentDescription
<id>project id Required.

Flags

FlagDescription
-e, --env <value>Environment to run against, e.g. production. Defaults to ZITADEL_ENV, then the hosting platform's build (VERCEL_ENV, or Netlify's CONTEXT), then development.
--env-file <value>Read ZITADEL_* values from this file ahead of the process environment. A relative path is read from the current directory, not from --cwd. Cannot be combined with --env.

Optional field flags

FlagDescription
--name <value>The name of the project.

Password hash field flags

FlagDescription
--password-hash-algorithm <value>(required with password_hash.*) The hashing algorithm. One of argon2i, argon2id, bcrypt, scrypt, pbkdf2, sha2.
--password-hash-params-time <value>argon2 passes over memory.
--password-hash-params-memory <value>argon2 memory in KiB.
--password-hash-params-threads <value>argon2 lanes.
--password-hash-params-cost <value>bcrypt cost, or scrypt's log2 of the CPU/memory cost.
--password-hash-params-rounds <value>pbkdf2 or sha2 iteration count.
--password-hash-params-hash <value>The underlying hash. One of sha1, sha224, sha256, sha384, sha512.

Raw body flags

FlagDescription
--data <value>Whole body as a JSON object. Field flags and --set apply over it. Not with --file.
--file <value>Read the body from a JSON file; - reads stdin. Field flags and --set apply over it. Not with --data.
--set <value>Set one field by its dot path: path=value, or path:=json for JSON. Repeatable; applied after the field flags, in order. A key that contains a dot is set through its parent: --set 'parent:={"a.b":"x"}'. Can be given more than once.

It also takes the global flags.

Examples

npx @zitadel/cli@latest projects update <id> --data '{...}' --json
npx @zitadel/cli@latest projects update <id> --file ./project.json

API

It calls Update project, PATCH /projects/{project_id}, in the Projects API.

Was this helpful?