Skip to content

Update master CLI reference docs for v2.6.0-rc.0.12.gba5d263 #1148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
haarchri merged 1 commit into from
Aug 30, 2026
+18 −1
Merged

Update master CLI reference docs for v2.6.0-rc.0.12.gba5d263 #1148

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion content/cli/master/command-reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ description: "Command reference for the Crossplane CLI"
<!-- vale Crossplane.Spelling = NO -->
<!-- vale cli-docs = YES -->

This documentation is for the `crossplane` CLI `v2.6.0-rc.0.2.g3d72f93`.
This documentation is for the `crossplane` CLI `v2.6.0-rc.0.12.gba5d263`.


<!-- vale Google.Headings = NO -->
Expand Down Expand Up @@ -1354,6 +1354,15 @@ multiple projects side-by-side.
You can use a Crossplane version other than the latest stable version by
specifying the `--crossplane-version` flag.

By default Crossplane installs a wildcard `ManagedResourceActivationPolicy`,
which activates the CRDs for every managed resource its providers offer. Pass
`--no-default-mrap` to skip it, so the control plane activates only the managed
resources your project declares its own activation policies for. This matches
what a production control plane looks like when it manages activation
explicitly. Like `--cluster-admin`, this flag applies only when `run` creates
the control plane. A control plane that already runs Crossplane keeps its
original settings, so run `crossplane project stop` first to change them.

You can provide resources to apply around the project install:

- `--init-resources` applies one or more files *before* installing the
Expand Down Expand Up @@ -1381,6 +1390,13 @@ Pin the Crossplane version installed in the dev control plane:
crossplane project run --crossplane-version=v2.2.1
```

Run without the default wildcard activation policy, so only the project's own
`ManagedResourceActivationPolicy` resources activate CRDs:

```shell
crossplane project run --no-default-mrap
```

Apply `imageconfig.yaml` before installing the Configuration, and
`providerconfig.yaml` after:

Expand All @@ -1406,6 +1422,7 @@ crossplane project run [flags]
| | `--crossplane-version=STRING` | Version of Crossplane to install. |
| | `--registry-dir=STRING` | Directory for local registry images. |
| | `--cluster-admin` | Grant Crossplane the cluster-admin role. |
| | `--default-mrap` | Install the default wildcard ManagedResourceActivationPolicy in the dev control plane. |
| | `--timeout=5m` | Max wait for project readiness. |
| | `--init-resources=INIT-RESOURCES` | Resources to apply before installing. |
| | `--extra-resources=EXTRA-RESOURCES` | Resources to apply after installing. |
Expand Down
Loading