v0.3.12: Add AWS cross-account parameters and comprehensive documentation update

- Add aws_session_name and aws_role_name parameters to model resource
- Comprehensive documentation overhaul with consolidated examples
- Update vector store documentation to reflect only officially supported LiteLLM providers
- Clean up project structure by removing scattered example files
- Update provider source references and enhance all resource documentation

Author: Nicholas Cecere

CHANGELOG.md

@@ -7,6 +7,34 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.3.12] - 2025-08-13
+
+### Added
+- **New AWS Parameters**: Added `aws_session_name` and `aws_role_name` to model resource for cross-account access scenarios
+  - Support for AWS session names in cross-account access configurations
+  - Support for AWS IAM role names for cross-account access
+  - Enhanced AWS Bedrock integration capabilities
+
+### Changed
+- **Documentation Overhaul**: Comprehensive update to all provider documentation
+  - Updated provider source references from `bitop/litellm` to `registry.terraform.io/ncecere/litellm`
+  - Consolidated all scattered example files into organized documentation structure
+  - Enhanced all resource documentation with multiple real-world examples
+  - Added comprehensive cross-resource integration examples
+- **Vector Store Documentation**: Updated to reflect only officially supported LiteLLM providers
+  - Removed unsupported providers (Pinecone, Weaviate, Chroma, Qdrant, Milvus, FAISS)
+  - Added accurate examples for supported providers: AWS Bedrock Knowledge Bases, OpenAI Vector Stores, Azure Vector Stores, Vertex AI RAG Engine, PG Vector
+  - Updated provider-specific parameters with correct configurations
+  - Added references to official LiteLLM documentation
+- **Project Organization**: Cleaned up project structure
+  - Removed scattered example files from root directory
+  - Consolidated all examples into comprehensive documentation
+  - Updated README.md to reflect current capabilities and structure
+
+### Fixed
+- Corrected vector store provider documentation to match LiteLLM's official capabilities
+- Updated all documentation links and references for accuracy
+
 ## [0.3.11] - 2025-08-10
 
 ### Added

README.md

@@ -130,6 +130,7 @@ For full details on the <code>litellm_key</code> resource, see the [key resource
 - <code>litellm_model</code>: Manage model configurations. [Documentation](docs/resources/model.md)
 - <code>litellm_team</code>: Manage teams. [Documentation](docs/resources/team.md)
 - <code>litellm_team_member</code>: Manage team members. [Documentation](docs/resources/team_member.md)
+- <code>litellm_team_member_add</code>: Add multiple members to teams. [Documentation](docs/resources/team_member_add.md)
 - <code>litellm_key</code>: Manage API keys. [Documentation](docs/resources/key.md)
 - <code>litellm_mcp_server</code>: Manage MCP (Model Context Protocol) servers. [Documentation](docs/resources/mcp_server.md)
 - <code>litellm_credential</code>: Manage credentials for secure authentication. [Documentation](docs/resources/credential.md)
@@ -212,6 +213,7 @@ This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENS
 ## Notes
 
 - Always use environment variables or secure secret management solutions to handle sensitive information like API keys and AWS credentials.
-- Refer to the `examples/` directory for more detailed usage examples.
+- Refer to the comprehensive documentation in the `docs/` directory for detailed usage examples and configuration options.
 - Make sure to keep your provider version updated for the latest features and bug fixes.
-- v0.2.3 introduces support for the <code>reasoning_effort</code> attribute in the <code>litellm_model</code> resource. This attribute accepts "low", "medium", or "high" to control the model's reasoning effort.
+- The provider now supports AWS cross-account access with `aws_session_name` and `aws_role_name` parameters in the model resource.
+- All example configurations have been consolidated into the documentation for better organization and maintenance.

docs/index.md

@@ -1,42 +1,64 @@
 # LiteLLM Provider
 
-The LiteLLM provider allows Terraform to manage LiteLLM resources. LiteLLM is a proxy service that standardizes the input/output across different LLM APIs.
+The LiteLLM provider allows Terraform to manage LiteLLM resources. LiteLLM is a proxy service that standardizes the input/output across different LLM APIs, providing a unified interface for various language model providers.
 
 ## Example Usage
 
 ```hcl
 terraform {
   required_providers {
     litellm = {
-      source  = "bitop/litellm"
-      version = "~> 0.2.3"
+      source = "registry.terraform.io/ncecere/litellm"
     }
   }
 }
 
 provider "litellm" {
-  api_base = "http://your-litellm-instance:4000"
-  api_key  = "your-api-key"
+  api_base = "https://your-litellm-proxy.com"
+  api_key  = var.litellm_api_key
 }
 
-# Example Model Configuration
-
-```hcl
-resource "litellm_model" "example" {
+# Basic model configuration
+resource "litellm_model" "gpt4" {
   model_name          = "gpt-4-proxy"
   custom_llm_provider = "openai"
   model_api_key       = var.openai_api_key
-  model_api_base      = "https://api.openai.com/v1"
   base_model          = "gpt-4"
   tier                = "paid"
   mode                = "chat"
-  reasoning_effort    = "medium"  # Optional: "low", "medium", or "high"
   
   input_cost_per_million_tokens  = 30.0
   output_cost_per_million_tokens = 60.0
 }
+
+# Team configuration
+resource "litellm_team" "dev_team" {
+  team_alias = "development-team"
+  models     = [litellm_model.gpt4.model_name]
+  max_budget = 100.0
+}
 ```
 
+## Available Resources
+
+The LiteLLM provider supports the following resources:
+
+* [`litellm_model`](./resources/model) - Manage LiteLLM model configurations
+* [`litellm_team`](./resources/team) - Manage teams and their permissions
+* [`litellm_team_member`](./resources/team_member) - Manage team member configurations
+* [`litellm_team_member_add`](./resources/team_member_add) - Add members to teams
+* [`litellm_key`](./resources/key) - Manage API keys
+* [`litellm_mcp_server`](./resources/mcp_server) - Manage MCP (Model Context Protocol) servers
+* [`litellm_credential`](./resources/credential) - Manage credentials for various providers
+* [`litellm_vector_store`](./resources/vector_store) - Manage vector stores
+
+## Available Data Sources
+
+The LiteLLM provider supports the following data sources:
+
+* [`litellm_credential`](./data-sources/credential) - Retrieve credential information
+* [`litellm_vector_store`](./data-sources/vector_store) - Retrieve vector store information
+
 ## Authentication
 
 The LiteLLM provider requires an API key and base URL for authentication. These can be provided in the provider configuration block or via environment variables.
@@ -46,9 +68,38 @@ The LiteLLM provider requires an API key and base URL for authentication. These
 - `LITELLM_API_BASE` - The base URL of your LiteLLM instance
 - `LITELLM_API_KEY` - Your LiteLLM API key
 
+### Example with Environment Variables
+
+```bash
+export LITELLM_API_BASE="https://your-litellm-proxy.com"
+export LITELLM_API_KEY="your-api-key"
+```
+
+```hcl
+terraform {
+  required_providers {
+    litellm = {
+      source = "registry.terraform.io/ncecere/litellm"
+    }
+  }
+}
+
+# Provider will automatically use environment variables
+provider "litellm" {}
+```
+
 ## Provider Arguments
 
 The following arguments are supported in the provider block:
 
 * `api_base` - (Required) The base URL of your LiteLLM instance. This can also be provided via the `LITELLM_API_BASE` environment variable.
 * `api_key` - (Required) The API key used to authenticate with LiteLLM. This can also be provided via the `LITELLM_API_KEY` environment variable.
+
+## Getting Started
+
+1. Install the provider by adding it to your Terraform configuration
+2. Configure your LiteLLM instance URL and API key
+3. Start creating resources like models, teams, and credentials
+4. Use data sources to reference existing configurations
+
+For detailed examples and configuration options, see the individual resource and data source documentation pages.

docs/resources/credential.md

@@ -12,6 +12,8 @@ Manages a LiteLLM credential for storing sensitive authentication information. C
 
 ## Example Usage
 
+### Basic OpenAI Credential
+
 ```terraform
 resource "litellm_credential" "openai_cred" {
   credential_name = "openai-api-key"
@@ -20,32 +22,55 @@ resource "litellm_credential" "openai_cred" {
   credential_info = {
     provider = "openai"
     region   = "us-east-1"
+    purpose  = "chat-completions"
+  }
+  
+  credential_values = {
+    api_key = var.openai_api_key
+    org_id  = var.openai_org_id
+  }
+}
+```
+
+### Anthropic Credential
+
+```terraform
+resource "litellm_credential" "anthropic_cred" {
+  credential_name = "anthropic-api-key"
+  
+  credential_info = {
+    provider = "anthropic"
+    purpose  = "text-generation"
   }
   
   credential_values = {
-    api_key = "sk-..."
-    org_id  = "org-..."
+    api_key = var.anthropic_api_key
   }
 }
 ```
 
-## Example Usage with Vector Store
+### Pinecone Vector Store Credential
 
 ```terraform
 resource "litellm_credential" "pinecone_cred" {
-  credential_name = "pinecone-api-key"
+  credential_name = "pinecone-production"
   
   credential_info = {
-    provider = "pinecone"
+    provider    = "pinecone"
     environment = "production"
+    region      = "us-east-1"
   }
   
   credential_values = {
-    api_key = "your-pinecone-api-key"
-    index_name = "your-index-name"
+    api_key    = var.pinecone_api_key
+    index_name = "document-embeddings"
   }
 }
+```
+
+### Using Credentials with Vector Store
 
+```terraform
 resource "litellm_vector_store" "example" {
   vector_store_name        = "my-vector-store"
   custom_llm_provider      = "pinecone"
@@ -60,6 +85,43 @@ resource "litellm_vector_store" "example" {
 }
 ```
 
+### Multiple Provider Credentials
+
+```terraform
+# AWS Bedrock credential
+resource "litellm_credential" "aws_bedrock" {
+  credential_name = "aws-bedrock-cred"
+  
+  credential_info = {
+    provider = "aws"
+    service  = "bedrock"
+    region   = "us-east-1"
+  }
+  
+  credential_values = {
+    aws_access_key_id     = var.aws_access_key_id
+    aws_secret_access_key = var.aws_secret_access_key
+    aws_region            = "us-east-1"
+  }
+}
+
+# Azure OpenAI credential
+resource "litellm_credential" "azure_openai" {
+  credential_name = "azure-openai-cred"
+  
+  credential_info = {
+    provider = "azure"
+    service  = "openai"
+  }
+  
+  credential_values = {
+    api_key      = var.azure_openai_key
+    api_base     = var.azure_openai_endpoint
+    api_version  = "2023-12-01-preview"
+  }
+}
+```
+
 ## Argument Reference
 
 The following arguments are supported: