-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update readme to include generate secret action.
- Loading branch information
Showing
7 changed files
with
95 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,5 @@ | ||
# vault integration pack | ||
|
||
> HashiCorp Vault | ||
steve.neuharth <[email protected]> | ||
### Contributors | ||
- Andy Moore <[email protected]> | ||
- Jacob Floyd <[email protected]> | ||
|
||
_HashiCorp Vault_ | ||
|
||
## Configuration | ||
|
||
|
@@ -36,6 +29,17 @@ _Delete value from Vault server_ | |
| Parameter | Type | Required | Secret | Description | | ||
|---|---|---|---|---| | ||
| `path` | string | True | default | _Path to delete from Vault_ | | ||
### generate_secret | ||
_Generate a secret and write it to vault._ | ||
| Parameter | Type | Required | Secret | Description | | ||
|---|---|---|---|---| | ||
| `profile_name` | string | False | default | _The profile to use to run this action._ | | ||
| `mount_point` | string | False | default | _Vault moint point in the URL_ | | ||
| `path` | string | True | default | _Path to the secrets_ | | ||
| `key_name` | string | True | default | _Name of the key to write the secret._ | | ||
| `update_tactic` | string | False | default | _The logic to use when writing secret to Vault. See readme for details._ | | ||
| `string_set` | string | default | default | _Unavailable_ | | ||
| `secret_length` | integer | default | default | _The number of characters to use in the secret._ | | ||
### read | ||
_Read value from Vault server_ | ||
| Parameter | Type | Required | Secret | Description | | ||
|
@@ -49,7 +53,7 @@ _Create a new Token_ | |
| Items are of type | |||| | ||
| `policies` | array | False | default | _List of policy names to associate with this token._ | | ||
| `meta` | string | False | default | _Metadata to associate with the token. This metadata will show in the audit log when the token is used._ | | ||
| `no_parent` | boolean | False | default | __ | | ||
| `no_parent` | boolean | False | default | _Unavailable_ | | ||
| `display_name` | string | False | default | _Name to associate with this token. This is a non-sensitive value that can be used to help identify created secrets (e.g. prefixes)._ | | ||
| `num_uses` | string | False | default | _Number of times this token can be used. After the last use, the token is automatically revoked._ | | ||
| `no_default_policy` | boolean | False | default | _Detach the 'default' policy from the policy set for this token._ | | ||
|
@@ -88,18 +92,61 @@ _Create a new Vault policy_ | |
| `rules` | string | True | default | _Policy rules_ | | ||
### list_policies | ||
_List Policies from Vault server_ | ||
### write_secret | ||
_Write a secret to Vault._ | ||
| Parameter | Type | Required | Secret | Description | | ||
|---|---|---|---|---| | ||
| `profile_name` | string | False | default | _The profile to use to run this action._ | | ||
| `mount_point` | string | False | default | _Vault moint point in the URL_ | | ||
| `path` | string | True | default | _Path to the secrets_ | | ||
| `key_name` | string | True | default | _Name of the key to write the secret._ | | ||
| `secret` | string | True | True | _Secret contents to be written._ | | ||
| `decode_json` | boolean | False | default | _Secret is formatted as a json and should be decode to be sent to Vault_ | | ||
| `update_tactic` | string | False | default | _The logic to use when writing secret to Vault. See readme for details._ | | ||
### is_initialized | ||
_Read initialization status from Vault server_ | ||
|
||
|
||
|
||
|
||
### generate secret | ||
|
||
This action is written to pre-populate keys with a random secret. | ||
|
||
The following string sets are available | ||
|
||
- ascii_letters | ||
```abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ``` | ||
- ascii_lowercase | ||
```abcdefghijklmnopqrstuvwxyz``` | ||
- ascii_uppercase | ||
```ABCDEFGHIJKLMNOPQRSTUVWXYZ``` | ||
- digits | ||
```0123456789``` | ||
- punctuation | ||
```!"#$%&\'()*+,-./:;<=>?@[\\]^_`{|}~``` | ||
- printable | ||
```0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ!"#$%&\'()*+,-./:;<=>?@[\\]^_`{|}~ \t\n\r\x0b\x0c``` | ||
- alphanumeric | ||
```abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789``` | ||
|
||
### Update tactic | ||
|
||
The update tactic allows control of how the action will update existing secrets. The currently supported | ||
tactics are: | ||
- `update`: Overwrite an existing secret. | ||
- `abstain`: Do not overwrite an existing secret. | ||
|
||
## Sensors | ||
|
||
There are no sensors available for this pack. | ||
|
||
|
||
## Authentication methods | ||
|
||
Authentication methods are defined per profile and are mutally exclusive. Only configure the | ||
method that should be used. | ||
|
||
### Supported | ||
- approle | ||
- token | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters