# Parameters, groups, and conditions

The parameter commands operate on selected client or server templates. With no
project filter, multi-project commands process every enabled configured target.

Examples use `example-project-id` as a physical Firebase project ID. The leading `=`
on `--project` requests an exact match.

## Read parameters

Get one parameter across projects:

```sh
fbrcm get feature_enabled --project '^acme-prod'
```

List parameters selected by search or an expression:

```sh
fbrcm get --search 'checkout'
fbrcm get --expr 'value == true'
```

Useful selectors include:

```text
--project, -p <query>  select template targets; repeatable
--filter, -f <query>   filter parameter keys; repeatable
--group <name>         include parameters in named groups; repeatable
--search <text>        search keys, descriptions, groups, and values
--expr <expression>    apply a typed expression
--update               revalidate caches before reading
```

When selection resolves to one visible template target, human output omits the
redundant Project column. This also applies with no project filter when only one
project is configured or a whitelist or blacklist leaves one visible project.
Machine output retains complete target context.

## Add and duplicate

```sh
fbrcm add checkout_enabled \
  --project '=example-project-id' \
  --type boolean \
  --value false \
  --description 'Enable the new checkout' \
  --draft

fbrcm duplicate checkout_enabled checkout_enabled_v2 \
  --project '=example-project-id' \
  --draft
```

Parameter types are string, boolean, number, and JSON. JSON values must be
valid JSON:

```sh
fbrcm add checkout_config \
  --type json \
  --value '{"enabled":false,"variant":"control"}' \
  --project '=example-project-id' \
  --dry-run
```

## Update

Update a known parameter:

```sh
fbrcm update checkout_enabled \
  --project '=example-project-id' \
  --type boolean \
  --value true \
  --dry-run
```

Omit the positional key only when filters deliberately select several
parameters:

```sh
fbrcm update \
  --project '^example-staging-' \
  --filter '^checkout_' \
  --type boolean \
  --value false \
  --dry-run
```

Always inspect the matched-item count and diff before applying a broad update.

## Delete

```sh
fbrcm delete old_checkout_flag \
  --project '=example-project-id' \
  --dry-run
```

Deleting a parameter does not remove an empty group. fbrcm preserves empty and
description-only groups unless you run an explicit group delete. It also blocks
parameter deletion for Firebase-managed and unknown future values.

## Manage groups

```sh
fbrcm groups list --project '=example-project-id'
fbrcm groups add checkout --description 'Checkout controls' --project '=example-project-id' --draft
fbrcm groups edit checkout \
  --description 'Checkout and payment controls' \
  --project '=example-project-id' \
  --draft
fbrcm groups rename checkout checkout_v2 --project '=example-project-id' --draft
fbrcm groups delete checkout_v2 --project '=example-project-id' --dry-run
```

Group names selected for edit, rename, or delete match exactly and
case-sensitively. Deleting a group removes all parameters inside it.

## Inspect conditions

```sh
fbrcm conditions list example-project-id
fbrcm conditions show example-project-id "iOS users"
fbrcm conditions validate example-project-id
```

The list follows Firebase evaluation order. `show` includes the parameters and
conditional values that reference the selected condition.

When a condition uses `app.id`, use [`apps list`](/cli/apps.md) to match its
Firebase App ID to a registered Android, iOS, or Web app.

## Change conditions

```sh
fbrcm conditions add example-project-id "Beta users" \
  --expression 'percent <= 10' \
  --color ORANGE \
  --draft

fbrcm conditions edit example-project-id "Beta users" \
  --expression 'percent <= 20' \
  --draft

fbrcm conditions move example-project-id "Beta users" 1 --draft
fbrcm conditions rename example-project-id "Beta users" "Early access" --draft
fbrcm conditions delete example-project-id "Early access" --dry-run

fbrcm conditions add "Beta users" \
  --project '=example-staging' \
  --project '=example-preview' \
  --expression 'percent <= 10' \
  --draft

fbrcm conditions delete \
  --project '^example-' \
  --expr 'usage_count == 0' \
  --dry-run
```

Rename updates every conditional-value reference. Delete removes the condition
and its conditional values. `add` and `delete` accept repeatable project filters;
without a positional project or project filters, they select every configured
project and enabled template. Delete also supports the same name, search, and
condition-expression filters as `conditions list`. Moving a condition can
change value resolution, so fbrcm treats it as a reviewed Remote Config mutation.

See [Filtering](/reference/filtering.md) for filter composition, expression
contexts, value typing, and JSON queries.