---
title: "plugin_publish"
---
## cloudquery plugin publish

Publish to CloudQuery Hub.

### Synopsis

Publish to CloudQuery Hub.

This publishes a plugin version to CloudQuery Hub from a local dist directory.


```
cloudquery plugin publish [-D dist] [flags]
```

### Examples

```

# Publish a plugin version from a local dist directory
cloudquery plugin publish
```

### Options

```
  -D, --dist-dir string   Path to the dist directory (default "dist")
  -f, --finalize          Finalize the plugin version after publishing. If false, the plugin version will be marked as draft.
  -h, --help              help for publish
  -U, --ui-dir string     Path to the built plugin UI directory
```

### Options inherited from parent commands

```
      --cq-dir string            directory to store cloudquery files, such as downloaded plugins (default ".cq")
      --invocation-id uuid       useful for when using Open Telemetry integration for tracing and logging to be able to correlate logs and traces through many services (default <NEW-RANDOM-UUID>)
      --log-console              enable console logging
      --log-file-name string     Log filename (default "cloudquery.log")
      --log-file-overwrite       Overwrite log file on each run instead of appending. Use this if your filesystem does not support append mode (e.g. FUSE-mounted cloud storage).
      --log-format string        Logging format (json, text) (default "text")
      --log-level string         Logging level (trace, debug, info, warn, error) (default "info")
      --no-log-file              Disable logging to file
      --telemetry-level string   Telemetry level (none, errors, stats, all) (default "all")
```

### SEE ALSO

* [cloudquery plugin](/cli/cli-reference/cloudquery_plugin)	 - Plugin commands


## See Also

- [Publishing an Integration](/cli/integrations/creating-new-integration/publishing) - Full publishing guide
- [Creating a New Integration](/cli/integrations/creating-new-integration) - Build an integration first
