fix documentation

Author: maxlaverse

docs/index.md

@@ -17,21 +17,21 @@ terraform {
   required_providers {
     bitwarden = {
       source  = "maxlaverse/bitwarden"
-      version = ">= 0.6.2"
+      version = ">= 0.6.1"
     }
   }
 }
 
 # Configure the Bitwarden Provider
 provider "bitwarden" {
-  email           = "terraform@example.com"
+  email = "terraform@example.com"
 }
 
 # Create a Bitwarden Login Resource
 resource "bitwarden_item_login" "example" {
-  name            = "Example"
-  username        = "service-account"
-  password        = "<sensitive>"
+  name     = "Example"
+  username = "service-account"
+  password = "<sensitive>"
 }
 ```
 
@@ -61,7 +61,7 @@ When doing so, it's your responsibility to:
 * 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
 
 # or if you use a custom vault path
@@ -74,7 +74,7 @@ Configuration for the Bitwarden Provider can be derived from two sources:
 * Environment variables
 
 ### Parameters
-Credentials can be provided by adding a `master_password` and optionally `client_id` and `client_secret` to the bitwarden provider block.
+Credentials can be provided by adding a combination of `email`, `master_password`, `client_id`, `client_secret` or `session_key` to the bitwarden provider block.
 ```terraform
 provider "bitwarden" {
   email           = "terraform@example.com"
@@ -85,7 +85,7 @@ provider "bitwarden" {
 ```
 
 ### Environment variables
-Credentials can be provided by using the `BW_PASSWORD` and optionally `BW_CLIENTID` and `BW_CLIENTSECRET` environment variables. 
+Credentials can be provided by using a combination of `BW_EMAIL`, `BW_PASSWORD`, `BW_CLIENTID`, `BW_CLIENTSECRET` or `BW_SESSION` environment variables. 
 
 For example:
 ```bitwarden

examples/quick/provider.tf

@@ -9,12 +9,12 @@ terraform {
 
 # Configure the Bitwarden Provider
 provider "bitwarden" {
-  email           = "terraform@example.com"
+  email = "terraform@example.com"
 }
 
 # Create a Bitwarden Login Resource
 resource "bitwarden_item_login" "example" {
-  name            = "Example"
-  username        = "service-account"
-  password        = "<sensitive>"
+  name     = "Example"
+  username = "service-account"
+  password = "<sensitive>"
 }

templates/index.md.tmpl

@@ -40,7 +40,7 @@ When doing so, it's your responsibility to:
 * 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
 
 # or if you use a custom vault path
@@ -53,7 +53,7 @@ Configuration for the Bitwarden Provider can be derived from two sources:
 * Environment variables
 
 ### Parameters
-Credentials can be provided by adding a `master_password` and optionally `client_id` and `client_secret` to the bitwarden provider block.
+Credentials can be provided by adding a combination of `email`, `master_password`, `client_id`, `client_secret` or `session_key` to the bitwarden provider block.
 ```terraform
 provider "bitwarden" {
   email           = "terraform@example.com"
@@ -64,7 +64,7 @@ provider "bitwarden" {
 ```
 
 ### Environment variables
-Credentials can be provided by using the `BW_PASSWORD` and optionally `BW_CLIENTID` and `BW_CLIENTSECRET` environment variables. 
+Credentials can be provided by using a combination of `BW_EMAIL`, `BW_PASSWORD`, `BW_CLIENTID`, `BW_CLIENTSECRET` or `BW_SESSION` environment variables. 
 
 For example:
 ```bitwarden