prepare release v0.13.2

Author: maxlaverse

README.md

@@ -14,6 +14,7 @@ This project is not associated with the Bitwarden project nor Bitwarden, Inc.
 ---
 
 ## Table of Contents
+
 - [Supported Versions](#supported-versions)
 - [Usage](#usage)
 - [Embedded Client](#embedded-client)
@@ -22,7 +23,9 @@ This project is not associated with the Bitwarden project nor Bitwarden, Inc.
 - [License](#license)
 
 ## Supported Versions
+
 The plugin has been tested and built with the following components:
+
 - [Terraform] v1.9.8 / [OpenTofu] v1.9.0
 - [Bitwarden CLI] v2023.2.0 (when not using the [Embedded Client](#embedded-client))
 - [Go] 1.23.4 (for development)
@@ -40,7 +43,7 @@ terraform {
   required_providers {
     bitwarden = {
       source  = "maxlaverse/bitwarden"
-      version = ">= 0.13.0"
+      version = ">= 0.13.2"
     }
   }
 }
@@ -80,26 +83,30 @@ data "bitwarden_item_login" "example" {
 See the [examples](./examples/) directory for more examples.
 
 ## Embedded Client
+
 Since version 0.9.0, the provider contains an embedded client that can directly interact with Bitwarden's API, removing the need for a locally installed Bitwarden CLI.
 The embedded client makes the provider faster, easier to use, but it still requires more testing.
 For now, a feature flag needs to be set in order to use it (`experimental.embedded_client`), with the goal of having it the default in v1.0.0.
 
 ## Security Considerations
-When not using the [Embedded Client](#embedded-client), the provider downloads the encrypted Vault locally during *plan* or *apply* operations as would the Bitwarden CLI if you used it directly.
+
+When not using the [Embedded Client](#embedded-client), the provider downloads the encrypted Vault locally during _plan_ or _apply_ operations as would the Bitwarden CLI if you used it directly.
 Currently, the Terraform SDK doesn't offer a way to remove the encrypted Vault once changes have been applied.
 The issue [hashicorp/terraform-plugin-sdk#63] tracks discussions for adding such a feature.
 
 If you want find out more about this file, you can read [Terraform's documentation on Data Storage].
 Please note that this file is stored at `<your-project>/.bitwarden/` by default, in order to not interfere with your local Vaults.
 
 ## Developing the Provider
+
 If you wish to work on the provider, you'll first need [Go](http://www.golang.org) installed on your machine (see [Requirements](#requirements) above).
 
 To compile the provider, run `go install`. This will build the provider and put the provider binary in the `$GOPATH/bin` directory.
 
 To generate or update documentation, run `go generate`.
 
 In order to run the full suite of Acceptance tests, start a Vaultwarden server:
+
 ```sh
 $ make server
 ```
@@ -110,8 +117,8 @@ Then run `make testacc`.
 $ make testacc
 ```
 
-
 ## License
+
 Distributed under the Mozilla License. See [LICENSE](./LICENSE) for more information.
 
 [Bitwarden CLI]: https://bitwarden.com/help/article/cli/#download-and-install

docs/index.md

@@ -18,7 +18,7 @@ terraform {
   required_providers {
     bitwarden = {
       source  = "maxlaverse/bitwarden"
-      version = ">= 0.13.0"
+      version = ">= 0.13.2"
     }
   }
 }
@@ -51,20 +51,25 @@ data "bitwarden_item_login" "example" {
 ```
 
 ## Authentication
+
 Depending on the type of credentials you use, you'll be able to connect either with a Password Manager or Secret Manager.
 If you want your workspace to interact with both, have a look at [provider aliases].
 
 ### Password Manager
+
 The Password Manager accepts different combinations of credentials to authenticate:
-* _[Personal API Key]_ (requires `master_password`, `client_id` and `client_secret` to be set).
-* _Email and Password_ (requires `email` and `master_password` to be set) (prefer _Personal API keys_ instead).
-* User-provided _Session Key_ (requires `session_key` to be set), which only works with a pre-downloaded Vault (See _Generating a Session Key_).
+
+- _[Personal API Key]_ (requires `master_password`, `client_id` and `client_secret` to be set).
+- _Email and Password_ (requires `email` and `master_password` to be set) (prefer _Personal API keys_ instead).
+- User-provided _Session Key_ (requires `session_key` to be set), which only works with a pre-downloaded Vault (See _Generating a Session Key_).
 
 #### Generating a Client ID and Secret
+
 The recommended way to interact with your Password Manager Vault using the Bitwarden Provider Terraform plugin is to generate an API key.
 This allows you to easily revoke access to your Vault without having to change your master password.
 
 In order to generate a pair of Client ID and Secret, you need to:
+
 1. Connect to your Vault on https://vault.bitwarden.com, or your self-hosted instance
 2. Click on _Settings_ and then _My Account_
 3. Scroll down to the _API Key_ section
@@ -75,11 +80,13 @@ In order to generate a pair of Client ID and Secret, you need to:
 
 If you don't want to use an API key, you can use a Session Key instead.
 When doing so, it's your responsibility to:
-* ensure the validity of the Session Key
-* keep the Session Key safe
-* revoke it when you don't need it anymore
+
+- ensure the validity of the Session Key
+- keep the Session Key safe
+- revoke it when you don't need it anymore
 
 You can generate a Session Key by running the following command in your Terraform Workspace:
+
 ```console
 BITWARDENCLI_APPDATA_DIR=.bitwarden bw login
 
@@ -90,9 +97,11 @@ BITWARDENCLI_APPDATA_DIR=<vault_path> bw login
 A Session Key is bound to a local copy of a Vault. It's therefore important that you set the right `BITWARDENCLI_APPDATA_DIR` to the path where your Vault is stored.
 
 ### Secrets Manager
+
 The Secrets Manager only accepts [Access Tokens] (requires `access_token` to be set).
 
 In order to generate an Access Token you need to:
+
 1. Connect to your Vault on https://vault.bitwarden.com
 2. Ensure the _Secrets Manager_ section is selected (bottom left)
 3. Click on _Machine accounts_
@@ -101,14 +110,17 @@ In order to generate an Access Token you need to:
 6. Select the _Access Tokens_ tab
 7. Created a new Access Token and save it somewhere safe
 
-
 ## Configuration
+
 Configuration for the Bitwarden Provider can be derived from two sources:
-* Parameters in the provider configuration
-* Environment variables
+
+- Parameters in the provider configuration
+- Environment variables
 
 ### Parameters
+
 Credentials can be provided by adding a combination of `email`, `master_password`, `client_id`, `client_secret`, `access_token` or `session_key` to the bitwarden provider block.
+
 ```terraform
 provider "bitwarden" {
   email           = "terraform@example.com"
@@ -132,9 +144,11 @@ provider "bitwarden" {
 ```
 
 ### Environment variables
+
 Credentials can be provided by using a combination of `BW_EMAIL`, `BW_PASSWORD`, `BW_CLIENTID`, `BW_CLIENTSECRET`, `BWS_ACCESS_TOKEN` or `BW_SESSION` environment variables.
 
 For example:
+
 ```bitwarden
 provider "bitwarden" {}
 ```
@@ -147,6 +161,7 @@ export BW_CLIENTSECRET="my-client-secret"
 ```
 
 <!-- schema generated by tfplugindocs -->
+
 ## Schema
 
 ### Optional
@@ -163,6 +178,7 @@ export BW_CLIENTSECRET="my-client-secret"
 - `vault_path` (String) Alternative directory for storing the Vault locally (default: `.bitwarden/`, env: `BITWARDENCLI_APPDATA_DIR`).
 
 <a id="nestedblock--experimental"></a>
+
 ### Nested Schema for `experimental`
 
 Optional:

examples/quick/provider.tf

@@ -2,7 +2,7 @@ terraform {
   required_providers {
     bitwarden = {
       source  = "maxlaverse/bitwarden"
-      version = ">= 0.13.0"
+      version = ">= 0.13.2"
     }
   }
 }