@robinmordasiewicz/f5xc-terraform-mcp 3.5.1 → 3.6.1

package/README.md

@@ -1,332 +1,153 @@
-# F5 Distributed Cloud Terraform MCP Server
+# MCP Registry
 
-[![npm version](https://img.shields.io/npm/v/@robinmordasiewicz/f5xc-terraform-mcp)](https://www.npmjs.com/package/@robinmordasiewicz/f5xc-terraform-mcp)
-[![MIT License](https://img.shields.io/badge/License-MIT-yellow)](LICENSE)
+The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
 
-Token-optimized Model Context Protocol (MCP) server for F5 Distributed Cloud Terraform provider documentation, API specifications, and subscription management.
+[**📤 Publish my MCP server**](docs/modelcontextprotocol-io/quickstart.mdx) | [**⚡️ Live API docs**](https://registry.modelcontextprotocol.io/docs) | [**👀 Ecosystem vision**](docs/design/ecosystem-vision.md) | 📖 **[Full documentation](./docs)**
 
-This MCP server exposes tools for AI assistants to interact with the [F5 Distributed Cloud Terraform Provider](https://github.com/robinmordasiewicz/terraform-provider-f5xc), enabling intelligent infrastructure-as-code assistance.
+## Development Status
 
-## Features
+**2025-10-24 update**: The Registry API has entered an **API freeze (v0.1)** 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
 
-- **270+ OpenAPI Specifications** - Complete F5XC API documentation for AI-assisted configuration
-- **250+ Terraform Resources** - Full documentation for all provider resources and data sources
-- **Token-Optimized Design** - 14 tools consolidated to 7 (~75% token reduction)
-- **Subscription Tier Management** - Check feature availability across STANDARD/ADVANCED/PREMIUM tiers
-- **Addon Service Workflows** - Manage F5XC service activations
-- **Resource Metadata** - Deterministic AI configuration generation with validation rules, defaults, and one-of schemas
+**2025-09-08 update**: The registry has launched in preview 🎉 ([announcement blog post](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/)). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in [GitHub discussions](https://github.com/modelcontextprotocol/registry/discussions/new?category=ideas) or in the [#registry-dev Discord](https://discord.com/channels/1358869848138059966/1369487942862504016) ([joining details here](https://modelcontextprotocol.io/community/communication)).
 
-## Installation
+Current key maintainers:
+- **Adam Jones** (Anthropic) [@domdomegg](https://github.com/domdomegg)  
+- **Tadas Antanavicius** (PulseMCP) [@tadasant](https://github.com/tadasant)
+- **Toby Padilla** (GitHub) [@toby](https://github.com/toby)
+- **Radoslav (Rado) Dimitrov** (Stacklok) [@rdimitrov](https://github.com/rdimitrov)
 
-### Global Installation
+## Contributing
 
-```bash
-npm install -g @robinmordasiewicz/f5xc-terraform-mcp
-```
+We use multiple channels for collaboration - see [modelcontextprotocol.io/community/communication](https://modelcontextprotocol.io/community/communication).
 
-### Usage with Claude Desktop
+Often (but not always) ideas flow through this pipeline:
 
-Add to your `claude_desktop_config.json`:
+- **[Discord](https://modelcontextprotocol.io/community/communication)** - Real-time community discussions
+- **[Discussions](https://github.com/modelcontextprotocol/registry/discussions)** - Propose and discuss product/technical requirements
+- **[Issues](https://github.com/modelcontextprotocol/registry/issues)** - Track well-scoped technical work  
+- **[Pull Requests](https://github.com/modelcontextprotocol/registry/pulls)** - Contribute work towards issues
 
-```json
-{
-  "mcpServers": {
-    "f5xc-terraform": {
-      "command": "npx",
-      "args": ["-y", "@robinmordasiewicz/f5xc-terraform-mcp"]
-    }
-  }
-}
-```
+### Quick start:
 
-### Manual CLI Usage
+#### Pre-requisites
 
-```bash
-# Run the MCP server
-npx @robinmordasiewicz/f5xc-terraform-mcp
+- **Docker**
+- **Go 1.24.x**
+- **ko** - Container image builder for Go ([installation instructions](https://ko.build/install/))
+- **golangci-lint v2.4.0**
 
-# Or install globally and run directly
-f5xc-terraform-mcp
-```
+#### Running the server
 
-## Available Tools
-
-| Tool | Description |
-|------|-------------|
-| `f5xc_terraform_discover` | Meta-tool for discovering available tools with optional schema details |
-| `f5xc_terraform_docs` | Search, get, or list documentation (resources, data-sources, functions, guides) |
-| `f5xc_terraform_api` | Query 270+ OpenAPI specs (search, get, find endpoints, schema definitions) |
-| `f5xc_terraform_subscription` | Check subscription tier requirements for resources and properties |
-| `f5xc_terraform_addon` | Manage addon services (list, check activation, workflow) |
-| `f5xc_terraform_metadata` | Resource metadata for deterministic AI config generation |
-| `f5xc_terraform_get_summary` | Get provider summary with documentation and API specs overview |
-
-## Tool Details
-
-### Documentation Tool (`f5xc_terraform_docs`)
-
-Search and retrieve Terraform provider documentation.
-
-```typescript
-// Search for resources
-await f5xc_terraform_docs({
-  operation: "search",
-  query: "http_loadbalancer",
-  type: "resource",
-  limit: 10
-});
-
-// Get specific resource documentation
-await f5xc_terraform_docs({
-  operation: "get",
-  name: "http_loadbalancer",
-  type: "resource"
-});
-
-// List all resources
-await f5xc_terraform_docs({
-  operation: "list",
-  type: "resource"
-});
+```bash
+# Start full development environment
+make dev-compose
 ```
 
-### API Specification Tool (`f5xc_terraform_api`)
-
-Query OpenAPI specifications for API details.
-
-```typescript
-// Search API specs
-await f5xc_terraform_api({
-  operation: "search",
-  query: "http_loadbalancer",
-  limit: 10
-});
-
-// Get full spec with endpoints
-await f5xc_terraform_api({
-  operation: "get",
-  name: "http_loadbalancer",
-  include_paths: true,
-  include_definitions: false
-});
-
-// Find endpoints matching pattern
-await f5xc_terraform_api({
-  operation: "find_endpoints",
-  pattern: "/namespaces",
-  method: "GET"
-});
-
-// Get schema definition
-await f5xc_terraform_api({
-  operation: "get_definition",
-  spec_name: "http_loadbalancer",
-  definition_name: "HTTPLoadBalancerSpec"
-});
-```
+This starts the registry at [`localhost:8080`](http://localhost:8080) with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
 
-### Subscription Tool (`f5xc_terraform_subscription`)
+**Note:** The registry uses [ko](https://ko.build) to build container images. The `make dev-compose` command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
 
-Check subscription tier requirements.
+By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with `MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose`.
 
-```typescript
-// Get resource tier requirements
-await f5xc_terraform_subscription({
-  operation: "resource",
-  resource_name: "http_loadbalancer"
-});
+The setup can be configured with environment variables in [docker-compose.yml](./docker-compose.yml) - see [.env.example](./.env.example) for a reference.
 
-// Check if property requires Advanced tier
-await f5xc_terraform_subscription({
-  operation: "property",
-  resource_name: "http_loadbalancer",
-  property_path: "enable_malicious_user_detection"
-});
-```
+<details>
+<summary>Alternative: Running a pre-built Docker image</summary>
 
-### Addon Service Tool (`f5xc_terraform_addon`)
+Pre-built Docker images are automatically published to GitHub Container Registry:
 
-Manage F5XC addon services.
-
-```typescript
-// List available addon services
-await f5xc_terraform_addon({
-  operation: "list"
-});
-
-// Check service activation status
-await f5xc_terraform_addon({
-  operation: "check",
-  service_name: "wasm"
-});
-
-// Get activation workflow guidance
-await f5xc_terraform_addon({
-  operation: "workflow",
-  service_name: "security_app_protect"
-});
-```
-
-### Metadata Tool (`f5xc_terraform_metadata`)
-
-Get resource metadata for deterministic AI configuration.
-
-```typescript
-// Get one-of field options
-await f5xc_terraform_metadata({
-  operation: "oneof",
-  resource: "http_loadbalancer",
-  attribute: "http_type"
-});
-
-// Get validation patterns
-await f5xc_terraform_metadata({
-  operation: "validation",
-  pattern: "name"
-});
-
-// Get default values
-await f5xc_terraform_metadata({
-  operation: "defaults",
-  resource: "namespace"
-});
-
-// Get enums
-await f5xc_terraform_metadata({
-  operation: "enums",
-  resource: "http_loadbalancer"
-});
-
-// Check attribute properties
-await f5xc_terraform_metadata({
-  operation: "attribute",
-  resource: "http_loadbalancer",
-  attribute: "name"
-});
-
-// Check requires_replace
-await f5xc_terraform_metadata({
-  operation: "requires_replace",
-  resource: "http_loadbalancer",
-  attribute: "name"
-});
-
-// Get resource dependencies
-await f5xc_terraform_metadata({
-  operation: "dependencies",
-  resource: "http_loadbalancer"
-});
-
-// Get troubleshooting info
-await f5xc_terraform_metadata({
-  operation: "troubleshoot",
-  error_code: "NOT_FOUND"
-});
-
-// Get full resource summary
-await f5xc_terraform_metadata({
-  operation: "summary",
-  resource: "namespace"
-});
-```
+```bash
+# Run latest stable release
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
 
-## Response Format
+# Run latest from main branch (continuous deployment)
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
 
-All tools support both `markdown` (default) and `json` response formats:
+# Run specific release version
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
 
-```typescript
-await f5xc_terraform_get_summary({
-  response_format: "json"
-});
+# Run development build from main branch
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d
 ```
 
-## Token Optimization
+**Available tags:** 
+- **Releases**: `latest`, `v1.0.0`, `v1.1.0`, etc.
+- **Continuous**: `main` (latest main branch build)
+- **Development**: `main-<date>-<sha>` (specific commit builds)
 
-This MCP server uses a token-optimized design:
+</details>
 
-- **14 original tools consolidated to 7** (~75% token reduction)
-- **Discovery meta-tool** enables lazy schema loading
-- **Shared parameter descriptions** reduce schema size
-- **Response truncation** for large payloads (50,000 character limit)
+#### Publishing a server
 
-## F5XC Provider Quick Start
+To publish a server, we've built a simple CLI. You can use it with:
 
-For Terraform configuration:
-
-```hcl
-terraform {
-  required_providers {
-    f5xc = {
-      source  = "robinmordasiewicz/f5xc"
-      version = ">= 2.0.0"
-    }
-  }
-}
-
-provider "f5xc" {
-  api_url   = "https://your-tenant.console.ves.volterra.io"
-  api_token = var.f5xc_api_token
-}
+```bash
+# Build the latest CLI
+make publisher
 
-# Create a namespace
-resource "f5xc_namespace" "example" {
-  name = "my-namespace"
-}
+# Use it!
+./bin/mcp-publisher --help
 ```
 
-## Resources Supported
-
-- **250+ Terraform Resources** - Full CRUD for F5XC services
-- **40+ Data Sources** - Read-only access to F5XC configurations
-- **2 Provider Functions** - `blindfold` and `blindfold_file` for secret management
-- **Multiple Guides** - Step-by-step tutorials for common use cases
-
-## Subscription Tiers
-
-F5XC resources are organized by subscription tier:
-
-| Tier | Description |
-|------|-------------|
-| **STANDARD** | Core networking and security features |
-| **ADVANCED** | Enhanced WAF, bot defense, and advanced security |
-| **PREMIUM** | Enterprise features and dedicated support |
+See [the publisher guide](./docs/modelcontextprotocol-io/quickstart.mdx) for more details.
 
-Use the subscription tool to check which tier a resource or feature requires.
+#### Other commands
 
-## Documentation
-
-- [Terraform Provider Documentation](https://registry.terraform.io/providers/robinmordasiewicz/f5xc/latest/docs)
-- [F5 Distributed Cloud Docs](https://docs.cloud.f5.com/)
-- [MCP Protocol Documentation](https://modelcontextprotocol.io/)
+```bash
+# Run lint, unit tests and integration tests
+make check
+```
 
-## Version Synchronization
+There are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](./Makefile).
 
-This npm package version is automatically synchronized with GitHub releases. Both the Terraform provider and MCP server share the same version number for consistency.
+<!--
+For Claude and other AI tools: Always prefer make targets over custom commands where possible.
+-->
 
-## Development
+## Architecture
 
-```bash
-# Clone the repository
-git clone https://github.com/robinmordasiewicz/terraform-provider-f5xc.git
+### Project Structure
 
-# Navigate to MCP server directory
-cd mcp-server
+```
+├── cmd/                     # Application entry points
+│   └── publisher/           # Server publishing tool
+├── data/                    # Seed data
+├── deploy/                  # Deployment configuration (Pulumi)
+├── docs/                    # Documentation
+├── internal/                # Private application code
+│   ├── api/                 # HTTP handlers and routing
+│   ├── auth/                # Authentication (GitHub OAuth, JWT, namespace blocking)
+│   ├── config/              # Configuration management
+│   ├── database/            # Data persistence (PostgreSQL)
+│   ├── service/             # Business logic
+│   ├── telemetry/           # Metrics and monitoring
+│   └── validators/          # Input validation
+├── pkg/                     # Public packages
+│   ├── api/                 # API types and structures
+│   │   └── v0/              # Version 0 API types
+│   └── model/               # Data models for server.json
+├── scripts/                 # Development and testing scripts
+├── tests/                   # Integration tests
+└── tools/                   # CLI tools and utilities
+    └── validate-*.sh        # Schema validation tools
+```
 
-# Install dependencies
-npm install
+### Authentication
 
-# Build the server
-npm run build
+Publishing supports multiple authentication methods:
+- **GitHub OAuth** - For publishing by logging into GitHub
+- **GitHub OIDC** - For publishing from GitHub Actions
+- **DNS verification** - For proving ownership of a domain and its subdomains
+- **HTTP verification** - For proving ownership of a domain
 
-# Run in development mode with hot reload
-npm run dev
-```
+The registry validates namespace ownership when publishing. E.g. to publish...:
+- `io.github.domdomegg/my-cool-mcp` you must login to GitHub as `domdomegg`, or be in a GitHub Action on domdomegg's repos
+- `me.adamjones/my-cool-mcp` you must prove ownership of `adamjones.me` via DNS or HTTP challenge
 
-## License
+## Community Projects
 
-This project is licensed under the [MIT License](LICENSE).
+Check out [community projects](docs/community-projects.md) to explore notable registry-related work created by the community.
 
-## Support
+## More documentation
 
-- [GitHub Issues](https://github.com/robinmordasiewicz/terraform-provider-f5xc/issues)
-- [F5 Community](https://community.f5.com/)
+See the [documentation](./docs) for more details if your question has not been answered here!

package/dist/docs/data-sources/bgp.md

@@ -2,12 +2,12 @@
 page_title: "f5xc_bgp Data Source - terraform-provider-f5xc"
 subcategory: "Networking"
 description: |-
-  Manages a BGP resource in F5 Distributed Cloud for bgp object is the configuration for peering with external bgp servers. it is created by users in system namespace. configuration.
+  Manages a BGP resource in F5 Distributed Cloud for bgp routing policy is a list of rules containing match criteria and action to be applied. these rules help contol routes which are imported or exported to bgp peers. configuration.
 ---
 
 # f5xc_bgp (Data Source)
 
-Manages a BGP resource in F5 Distributed Cloud for bgp object is the configuration for peering with external bgp servers. it is created by users in system namespace. configuration.
+Manages a BGP resource in F5 Distributed Cloud for bgp routing policy is a list of rules containing match criteria and action to be applied. these rules help contol routes which are imported or exported to bgp peers. configuration.
 
 ~> **Note** For more information about this data source, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
 

package/dist/docs/data-sources/discovery.md

@@ -2,12 +2,12 @@
 page_title: "f5xc_discovery Data Source - terraform-provider-f5xc"
 subcategory: "Applications"
 description: |-
-  Manages a Discovery resource in F5 Distributed Cloud for api to create discovery object for a site or virtual site in system namespace. configuration.
+  Manages API discovery creates a new object in the storage backend for metadata.namespace. in F5 Distributed Cloud.
 ---
 
 # f5xc_discovery (Data Source)
 
-Manages a Discovery resource in F5 Distributed Cloud for api to create discovery object for a site or virtual site in system namespace. configuration.
+Manages API discovery creates a new object in the storage backend for metadata.namespace. in F5 Distributed Cloud.
 
 ~> **Note** For more information about this data source, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
 

package/dist/docs/data-sources/fast_acl.md

@@ -2,12 +2,12 @@
 page_title: "f5xc_fast_acl Data Source - terraform-provider-f5xc"
 subcategory: "Security"
 description: |-
-  Manages fast_acl object, fast_acl object contains rules to protect site from denial of service It has destination{destination IP, destination port) and references to fast_acl_rule in F5 Distributed Cloud.
+  Manages new Fast ACL rule, has specification to match source IP, source port and action to apply. in F5 Distributed Cloud.
 ---
 
 # f5xc_fast_acl (Data Source)
 
-Manages `fast_acl` object, `fast_acl` object contains rules to protect site from denial of service It has destination{destination IP, destination port) and references to `fast_acl_rule` in F5 Distributed Cloud.
+Manages new Fast ACL rule, has specification to match source IP, source port and action to apply. in F5 Distributed Cloud.
 
 ~> **Note** For more information about this data source, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
 

package/dist/docs/data-sources/fast_acl_rule.md

@@ -2,12 +2,12 @@
 page_title: "f5xc_fast_acl_rule Data Source - terraform-provider-f5xc"
 subcategory: "Security"
 description: |-
-  Manages new Fast ACL rule, fast_acl_rule has specification to match source IP, source port and action to apply. in F5 Distributed Cloud.
+  Manages new Fast ACL rule, has specification to match source IP, source port and action to apply. in F5 Distributed Cloud.
 ---
 
 # f5xc_fast_acl_rule (Data Source)
 
-Manages new Fast ACL rule, `fast_acl_rule` has specification to match source IP, source port and action to apply. in F5 Distributed Cloud.
+Manages new Fast ACL rule, has specification to match source IP, source port and action to apply. in F5 Distributed Cloud.
 
 ~> **Note** For more information about this data source, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
 

package/dist/docs/data-sources/irule.md

@@ -2,12 +2,12 @@
 page_title: "f5xc_irule Data Source - terraform-provider-f5xc"
 subcategory: "BIG-IP Integration"
 description: |-
-  Manages a Irule resource in F5 Distributed Cloud for desired state for big-ip irule service. configuration.
+  Manages iRule in a given namespace. If one already exists it will give an error. in F5 Distributed Cloud.
 ---
 
 # f5xc_irule (Data Source)
 
-Manages a Irule resource in F5 Distributed Cloud for desired state for big-ip irule service. configuration.
+Manages iRule in a given namespace. If one already exists it will give an error. in F5 Distributed Cloud.
 
 ~> **Note** For more information about this data source, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
 

package/dist/docs/data-sources/log_receiver.md

@@ -2,12 +2,12 @@
 page_title: "f5xc_log_receiver Data Source - terraform-provider-f5xc"
 subcategory: "Monitoring"
 description: |-
-  Manages new Log Receiver object. in F5 Distributed Cloud.
+  Manages new Global Log Receiver object. in F5 Distributed Cloud.
 ---
 
 # f5xc_log_receiver (Data Source)
 
-Manages new Log Receiver object. in F5 Distributed Cloud.
+Manages new Global Log Receiver object. in F5 Distributed Cloud.
 
 ~> **Note** For more information about this data source, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
 

package/dist/docs/data-sources/network_policy.md

@@ -2,12 +2,12 @@
 page_title: "f5xc_network_policy Data Source - terraform-provider-f5xc"
 subcategory: "Security"
 description: |-
-  Manages new network policy with configured parameters in specified namespace. in F5 Distributed Cloud.
+  Manages network policy rule with configured parameters in specified namespace. in F5 Distributed Cloud.
 ---
 
 # f5xc_network_policy (Data Source)
 
-Manages new network policy with configured parameters in specified namespace. in F5 Distributed Cloud.
+Manages network policy rule with configured parameters in specified namespace. in F5 Distributed Cloud.
 
 ~> **Note** For more information about this data source, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
 

package/dist/docs/data-sources/route.md

@@ -2,12 +2,12 @@
 page_title: "f5xc_route Data Source - terraform-provider-f5xc"
 subcategory: "Load Balancing"
 description: |-
-  Manages route object in a given namespace. Route object is list of route rules. Each rule has match condition to match incoming requests and actions to take on matching requests. Virtual host object has reference to route object. in F5 Distributed Cloud.
+  Manages route object in a given namespace. Route object is list of route rules. Each rule has match condition to match incoming requests and actions to take on matching requests. in F5 Distributed Cloud.
 ---
 
 # f5xc_route (Data Source)
 
-Manages route object in a given namespace. Route object is list of route rules. Each rule has match condition to match incoming requests and actions to take on matching requests. Virtual host object has reference to route object. in F5 Distributed Cloud.
+Manages route object in a given namespace. Route object is list of route rules. Each rule has match condition to match incoming requests and actions to take on matching requests. in F5 Distributed Cloud.
 
 ~> **Note** For more information about this data source, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
 

package/dist/docs/data-sources/site.md

@@ -2,12 +2,12 @@
 page_title: "f5xc_site Data Source - terraform-provider-f5xc"
 subcategory: "Uncategorized"
 description: |-
-  Manages a Site resource in F5 Distributed Cloud for gcp vpc site specification. configuration.
+  Manages a Site resource in F5 Distributed Cloud for aws vpc site specification. configuration.
 ---
 
 # f5xc_site (Data Source)
 
-Manages a Site resource in F5 Distributed Cloud for gcp vpc site specification. configuration.
+Manages a Site resource in F5 Distributed Cloud for aws vpc site specification. configuration.
 
 ~> **Note** For more information about this data source, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
 

package/dist/docs/resources/address_allocator.md

@@ -32,7 +32,7 @@ resource "f5xc_address_allocator" "example" {
   }
 
   # Resource-specific configuration
-  # Address Allocation Scheme. Decides the scheme to be used ...
+  # Decides the scheme to be used to allocate addresses from ...
   address_allocation_scheme {
     # Configure address_allocation_scheme settings
   }
@@ -58,11 +58,11 @@ resource "f5xc_address_allocator" "example" {
 
 ### Spec Argument Reference
 
-<a id="address-allocation-scheme"></a>&#x2022; [`address_allocation_scheme`](#address-allocation-scheme) - Optional Block<br>Address Allocation Scheme. Decides the scheme to be used to allocate addresses from the configured address pool<br>See [Address Allocation Scheme](#address-allocation-scheme) below for details.
+<a id="address-allocation-scheme"></a>&#x2022; [`address_allocation_scheme`](#address-allocation-scheme) - Optional Block<br>Decides the scheme to be used to allocate addresses from the configured address pool<br>See [Address Allocation Scheme](#address-allocation-scheme) below for details.
 
-<a id="address-pool"></a>&#x2022; [`address_pool`](#address-pool) - Optional List<br>Address Pool. Address pool from which the allocator carves out subnets or addresses to its clients
+<a id="address-pool"></a>&#x2022; [`address_pool`](#address-pool) - Optional List<br>Address pool from which the allocator carves out subnets or addresses to its clients
 
-<a id="mode"></a>&#x2022; [`mode`](#mode) - Optional String  Defaults to `LOCAL`<br>Possible values are `LOCAL`, `GLOBAL_PER_SITE_NODE`<br>[Enum: LOCAL|GLOBAL_PER_SITE_NODE] Allocator Mode. Mode of the address allocator Address allocator is for VERs within the local cluster or site Allocation is per site and then per node
+<a id="mode"></a>&#x2022; [`mode`](#mode) - Optional String  Defaults to `LOCAL`<br>Possible values are `LOCAL`, `GLOBAL_PER_SITE_NODE`<br>[Enum: LOCAL|GLOBAL_PER_SITE_NODE] Mode of the address allocator Address allocator is for VERs within the local cluster or site Allocation is per site and then per node
 
 <a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
 
@@ -78,11 +78,11 @@ In addition to all arguments above, the following attributes are exported:
 
 An [`address_allocation_scheme`](#address-allocation-scheme) block supports the following:
 
-<a id="unit-44a05d"></a>&#x2022; [`allocation_unit`](#unit-44a05d) - Optional Number<br>Allocation Unit. Prefix length indicating the size of each allocated subnet. For example, if this is specified as 30, subnets of /30 will be allocated from the given address pool
+<a id="unit-44a05d"></a>&#x2022; [`allocation_unit`](#unit-44a05d) - Optional Number<br>Prefix length indicating the size of each allocated subnet. For example, if this is specified as 30, subnets of /30 will be allocated from the given address pool
 
-<a id="offset-3d4118"></a>&#x2022; [`local_interface_address_offset`](#offset-3d4118) - Optional Number<br>Local Interface Address Offset. This is used to derive address for the local interface from the allocated subnet. If Local Interface Address Type is set to 'Offset from beginning of Subnet', this offset value is added to the allocated subnet and used as the local interface address. For example, if the allocated subnet is 169.254.0.0/30 and offset is set to 2 with Local Interface Address Type set to 'Offset from beginning of Subnet', local interface address of 169.254.0.2 is used. If Local Interface Address Type is set to 'Offset from end of Subnet', this offset value is subtracted from the end of the allocated subnet and used as the local interface address. For example, if the allocated subnet is 169.254.0.0/30 and offset is set to 1 with Local Interface Address Type set to 'Offset from end of Subnet', local interface address of 169.254.0.2 is used
+<a id="offset-3d4118"></a>&#x2022; [`local_interface_address_offset`](#offset-3d4118) - Optional Number<br>Used to derive address for the local interface from the allocated subnet. If Local Interface Address Type is set to 'Offset from beginning of Subnet', this offset value is added to the allocated subnet and used as the local interface address. For example, if the allocated subnet is
 
-<a id="type-3a6e24"></a>&#x2022; [`local_interface_address_type`](#type-3a6e24) - Optional String  Defaults to `LOCAL_INTERFACE_ADDRESS_OFFSET_FROM_SUBNET_BEGIN`<br>Possible values are `LOCAL_INTERFACE_ADDRESS_OFFSET_FROM_SUBNET_BEGIN`, `LOCAL_INTERFACE_ADDRESS_OFFSET_FROM_SUBNET_END`, `LOCAL_INTERFACE_ADDRESS_FROM_PREFIX`<br>[Enum: LOCAL_INTERFACE_ADDRESS_OFFSET_FROM_SUBNET_BEGIN|LOCAL_INTERFACE_ADDRESS_OFFSET_FROM_SUBNET_END|LOCAL_INTERFACE_ADDRESS_FROM_PREFIX] Local Interface Address Type. Dictates how local interface address is derived from the allocated subnet Use Nth address of the allocated subnet as the local interface address, N being the Local Interface Address Offset. For example, if the allocated subnet is 169.254.0.0/30, Local Interface Address Offset is set to 2 and Local Interface Address Type is set to 'Offset from beginning of Subnet', local address of 169.254.0.2 is used. Use Nth last address of the allocated subnet as the local interface address, N being the Local Interface Address Offset. For example, if the allocated subnet is 169.254.0.0/30, Local Interface Address Offset is set to 1 and Local Interface Address Type is set to 'Offset from end of Subnet', local address of 169.254.0.2 is used. This case is used for external_connector
+<a id="type-3a6e24"></a>&#x2022; [`local_interface_address_type`](#type-3a6e24) - Optional String  Defaults to `LOCAL_INTERFACE_ADDRESS_OFFSET_FROM_SUBNET_BEGIN`<br>Possible values are `LOCAL_INTERFACE_ADDRESS_OFFSET_FROM_SUBNET_BEGIN`, `LOCAL_INTERFACE_ADDRESS_OFFSET_FROM_SUBNET_END`, `LOCAL_INTERFACE_ADDRESS_FROM_PREFIX`<br>[Enum: LOCAL_INTERFACE_ADDRESS_OFFSET_FROM_SUBNET_BEGIN|LOCAL_INTERFACE_ADDRESS_OFFSET_FROM_SUBNET_END|LOCAL_INTERFACE_ADDRESS_FROM_PREFIX] Dictates how local interface address is derived from the allocated subnet Use Nth address of the allocated subnet as the local interface address, N being the Local Interface Address Offset. For example, if the allocated subnet is 169.254.0.0/30, Local Interface Address Offset is set to 2 and
 
 #### Timeouts