Robert Main
18f469105c
* Update website folder to indicate deprecation Adds an alert banner to the top of all MDX files within `/website` to indicate deprecation * Update website README
32 lines
1.6 KiB
Plaintext
32 lines
1.6 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Plugin configuration
|
|
description: >-
|
|
Learn about the plugin-specific parameter that configures a directory for Boundary to use for writing and executing its built-in plugins.
|
|
---
|
|
|
|
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
|
|
> [!IMPORTANT]
|
|
> **Documentation Update:** Product documentation previously located in `/website` has moved to the [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs) repository, where all product documentation is now centralized. Please make contributions directly to `web-unified-docs`, since changes to `/website` in this repository will not appear on developer.hashicorp.com.
|
|
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
|
|
|
|
# `plugin` stanza
|
|
|
|
The `plugin` stanza configures plugin-specific parameters. The plugin system is currently internal; over time, the intent is to provide a mechanism for third-party plugins to be able to be used.
|
|
Available plugins are currently bundled with Boundary and executed automatically.
|
|
|
|
There is currently one configuration parameter available:
|
|
|
|
```hcl
|
|
plugins {
|
|
execution_dir = "/var/run/boundary/plugin-exec"
|
|
}
|
|
```
|
|
|
|
- `execution_dir` - Specifies a directory that Boundary can use to write and
|
|
execute its built-in plugins. This value can be a direct directory string,
|
|
can refer to a file on disk (file://) from which a directory location will be
|
|
read; or an env var (env://) from which the directory location will be read.
|
|
This directory must be writeable by the Boundary user. If not set, Boundary will
|
|
attempt to create a suitable directory in the system temporary folder.
|