IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

add changelog entry for GCP KMS and OpenBao; update bao doc domain (#1481)

Browse Source 
Signed-off-by: ollevche <ollevche@gmail.com>
This commit is contained in:
Oleksandr Levchenkov 2024-04-10 14:41:29 +03:00 committed by GitHub
parent 5536f790fd
commit 7b68b7827f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CHANGELOG.md
View File

@ -10,6 +10,8 @@ STATE ENCRYPTION
* Available key providers:
* Passphrase, via pbkdf2 ([#1310](https://github.com/opentofu/opentofu/pull/1310))
* AWS KMS ([#1349](https://github.com/opentofu/opentofu/pull/1349))
* GCP KMS ([#1392](https://github.com/opentofu/opentofu/pull/1392))
* OpenBao ([#1436](https://github.com/opentofu/opentofu/pull/1436))
NEW FEATURES:
* Add support for a `removed` block that allows users to remove resources or modules from the state without destroying them. ([#1158](https://github.com/opentofu/opentofu/pull/1158))

6
website/docs/language/state/encryption.mdx
View File

@ -129,12 +129,12 @@ The following example illustrates a minimal configuration:
### OpenBao
This key provider uses the [OpenBao Transit Secret Engine](https://janma.github.io/openbao/docs/secrets/transit) to generate data keys. You can configure it as follows:
This key provider uses the [OpenBao Transit Secret Engine](https://openbao.org/docs/secrets/transit) to generate data keys. You can configure it as follows:
| Option | Description | Min. | Default |
|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------------------------|
| key_name *(required)* | Name of the transit encryption key to use to encrypt/decrypt the datakey. It should be [pre-configured](https://janma.github.io/openbao/docs/secrets/transit/#setup) in OpenBao server. | N/A | - |
| token | [Authorization Token](https://janma.github.io/openbao/docs/concepts/tokens/) to use when accessing OpenBao API. Available as `BAO_TOKEN` environment variable. | N/A | - |
| key_name *(required)* | Name of the transit encryption key to use to encrypt/decrypt the datakey. It should be [pre-configured](https://openbao.org/docs/secrets/transit/#setup) in OpenBao server. | N/A | - |
| token | [Authorization Token](https://openbao.org/docs/concepts/tokens/) to use when accessing OpenBao API. Available as `BAO_TOKEN` environment variable. | N/A | - |
| address | OpenBao server address to access the API. Available as `BAO_ADDR` environment variable. | N/A | https://127.0.0.1:8200 |
| transit_engine_path | Path at whick Transit Secret Engine enabled in OpenBao. | N/A | /transit |
| key_length | Number of bytes to generate as a key. Available options are `16`, `32` or `64` bytes. | 16 | 32 |