# bricks run

Plan and apply resources

## Synopsis

Plan and apply resources. If the --task flag is not provided it will run the command locally

```
bricks run [package] [flags]
```

## Options

```
      --apply                         Apply plan
      --auto-apply                    Run bricks plan and apply in a single step (no separate bricks plan phase)
      --deployment string             Deployment GUID representing the root deployment
      --deployment-state-key string   State reference key. Provided when working with a state is required
      --destroy                       Create destroy plan
      --disable-plan-reuse            Disable plan file reuse during apply
  -d, --dry                           Create dependency tree only, without running the plan
      --import-state                  Import existing state from remote backend into Bluebricks
      --incremental                   Skip planning and applying packages that have no diff from state
      --output string                 Destination for plan, state, and any other output file
      --props string                  A JSON string of properties to associate with the package. This way a IaC turning opinionated
      --props-file string             A pointer to a JSON file that include the properties to associate with the package
      --provider string               Cloud provider
      --secrets string                A JSON string of secrets to associate with the package. This way a IaC turning opinionated
      --secrets-file string           A pointer to a JSON file that include the secrets to associate with the package
      --task string                   Task GUID representing the workflow
      --token string                  Backend server-to-server token
      --verbose                       Indicates the CLI to print every step that is happening.
```

## Options inherited from parent commands

```
      --api-key string    API key for authentication (overrides JWT)
      --config string     config file (default is $HOME/.bricks/config.yaml)
  -h, --help              Print Help message for Bricks CLI
      --non-interactive   Suppresses interactive UI elements for non-interactive environments
  -v, --version           Print bricks CLI version
```

## SEE ALSO

* [bricks](https://github.com/bluebricks-dev/Bluebricks-Documentation/blob/main/cli-reference/bricks.md) -


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bluebricks.co/docs/bricks-cli/cli-reference/bricks_run.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.