-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathplugins.yaml
More file actions
30 lines (29 loc) · 1.11 KB
/
plugins.yaml
File metadata and controls
30 lines (29 loc) · 1.11 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
---
# This file defines the release configuration for each Vault plugin. The syntax
# is as follows:
#
# <plugin-name>:
# enterprise: <boolean>
# binary-release: <boolean>
# repository: <string>
#
# `enterprise` - When set to true, this indicates that the plugin is
# closed source and is only available with Vault Enterprise.
# `binary-release` - When set to true, this indicates that the plugin
# binary will be released on https://releases.hashicorp.com/.
# `repository` (optional) - When set, this is the GitHub repository from which the plugin
# is built. If unset, the plugin name is used.
# Enterprise-only plugins that release binaries
#
# These ent-only plugins have a license-enforcing mechanism in place
# for publishing as an external plugin, so we can set binary-release: true.
vault-plugin-1:
enterprise: true
binary-release: true
bundled: true
repository: vault-plugin-1
vault-plugin-2:
enterprise: true
binary-release: true
bundled: false
repository: vault-plugin-2