### Configure and Use Volcenginecc Provider with VPC Example Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/docs/index.md This example demonstrates how to configure the Volcenginecc Terraform provider and create a VPC resource. It includes setting up required providers, defining VPC parameters like name, CIDR block, and gateway settings, and then querying the created VPC. This snippet is specific to Terraform. ```shell terraform { required_providers { volcenginecc = { source = "volcengine/volcenginecc" version = "~> 0.0.1-beta" } } } # Create VPC resource "volcenginecc_vpc_vpc" "VPCDemo" { vpc_name = "vpc-demo" description = "VpcDemo Example" cidr_block = "192.168.0.0/24" support_ipv_4_gateway = true enable_ipv_6 = false project_name = "default" tags = [ { key = "env" value = "test" } ] } # Query VPC data "volcenginecc_vpc_vpc" "VpcVpcDataSource" { id = volcenginecc_vpc_vpc.VPCDemo.id } ``` -------------------------------- ### Configure Volcenginecc Provider with Environment Variables Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/docs/index.md This example demonstrates configuring the Volcenginecc provider by referencing environment variables for authentication. The provider block remains empty, relying on `VOLCENGINE_ACCESS_KEY`, `VOLCENGINE_SECRET_KEY`, and `VOLCENGINE_REGION` to be set in the environment. ```shell provider "volcenginecc" { } ``` -------------------------------- ### Configure and Use Volcenginecc Provider with VPC Example Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/README.md This snippet demonstrates how to configure the Volcenginecc provider in Terraform and then create a VPC resource with specified parameters. It also shows how to query the created VPC using a data source. Ensure Terraform 1.0.7 or later is used. ```shell # Configure the Volcenginecc Provider terraform { required_providers { volcenginecc = { source = "volcengine/volcenginecc" version = "~> 0.0.1" } } } # Create VPC resource "volcenginecc_vpc_vpc" "VPCDemo" { vpc_name = "vpc-demo" description = "VpcDemo Example" cidr_block = "192.168.0.0/24" support_ipv_4_gateway = true enable_ipv_6 = false project_name = "default" tags = [ { key = "env" value = "test" } ] } # Query VPC data "volcenginecc_vpc_vpc" "VpcVpcDataSource" { id = volcenginecc_vpc_vpc.VPCDemo.id } ``` -------------------------------- ### VPC Resource Management Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/README.md Examples for creating and querying VPC resources using the Volcenginecc Terraform provider. ```APIDOC ## VPC Resource Management ### Create VPC This resource can be configured with the following arguments: ### Method Terraform Resource Definition ### Endpoint N/A ### Parameters #### Path Parameters None #### Query Parameters None #### Request Body None ### Request Example ```terraform # Create VPC resource "volcenginecc_vpc_vpc" "VPCDemo" { vpc_name = "vpc-demo" description = "VpcDemo Example" cidr_block = "192.168.0.0/24" support_ipv_4_gateway = true enable_ipv_6 = false project_name = "default" tags = [ { key = "env" value = "test" } ] } ``` ### Response #### Success Response (200) VPC resource is created. #### Response Example N/A ### Query VPC This data source can be configured with the following arguments: ### Method Terraform Data Source Definition ### Endpoint N/A ### Parameters #### Path Parameters None #### Query Parameters None #### Request Body None ### Request Example ```terraform # Query VPC data "volcenginecc_vpc_vpc" "VpcVpcDataSource" { id = volcenginecc_vpc_vpc.VPCDemo.id } ``` ### Response #### Success Response (200) VPC resource details are retrieved. #### Response Example N/A ``` -------------------------------- ### Import Existing Volcengine Resources with Terraform Source: https://context7.com/volcengine/terraform-provider-volcenginecc/llms.txt Demonstrates how to import pre-existing Volcengine resources into Terraform state management. It provides examples for importing VPCs, ECS instances, ALBs, RDS instances, and Redis instances, followed by commands to show the imported configuration and verify the state. ```bash # Import VPC terraform import volcenginecc_vpc_vpc.existing "vpc-2fe6g8ft83l450x58jdfxxx" # Import ECS instance terraform import volcenginecc_ecs_instance.existing "i-abc123xyz456" # Import ALB terraform import volcenginecc_alb_load_balancer.existing "alb-xyz789abc123" # Import RDS instance terraform import volcenginecc_rdsmysql_instance.existing "mysql-instance-id-123" # Import Redis instance terraform import volcenginecc_redis_instance.existing "redis-instance-id-456" # After import, generate configuration terraform show -no-color > imported.tf # Verify imported state terraform plan # Expected output: No changes. Infrastructure is up-to-date. ``` -------------------------------- ### Set Volcengine Credentials via Environment Variables Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/docs/index.md This example illustrates how to set the necessary Volcengine credentials and region using environment variables in a shell environment. These variables are then used by the Volcenginecc Terraform provider for authentication when they are not explicitly provided in the configuration. ```shell $ export VOLCENGINE_ACCESS_KEY="your_public_key" $ export VOLCENGINE_SECRET_KEY="your_private_key" $ export VOLCENGINE_REGION="cn-beijing" ``` -------------------------------- ### Volcenginecc Provider Environment Variable Authentication Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/README.md This example illustrates configuring the Volcenginecc provider to use credentials sourced from environment variables (VOLCENGINE_ACCESS_KEY, VOLCENGINE_SECRET_KEY, VOLCENGINE_REGION). This is a more secure method than hard-coding credentials. ```shell provider "volcenginecc" { } ``` ```shell $ export VOLCENGINE_ACCESS_KEY="your_public_key" $ export VOLCENGINE_SECRET_KEY="your_private_key" $ export VOLCENGINE_REGION="cn-beijing" ``` -------------------------------- ### Configure Volcengine Provider with Environment Variables in Terraform Source: https://context7.com/volcengine/terraform-provider-volcenginecc/llms.txt This example shows how to configure the Volcengine Terraform provider by setting credentials via environment variables. Terraform automatically detects and uses these variables, simplifying the provider configuration block. It also includes the steps to set the variables and apply a Terraform configuration for an ECS instance. ```bash # Set environment variables export VOLCENGINE_ACCESS_KEY="your_access_key" export VOLCENGINE_SECRET_KEY="your_secret_key" export VOLCENGINE_REGION="cn-beijing" # Terraform configuration - provider auto-detects env vars cat > main.tf <) - The IDs of the security groups. - **status** (String) - The status of the ECS instance. - **public_ip_address** (String) - The public IP address of the ECS instance. - **private_ip_address** (String) - The private IP address of the ECS instance. #### Response Example ```json { "instance_id": "i-abcdef1234567890", "instance_name": "my-ecs-instance", "instance_type": "ecs.g1.large", "zone_id": "cn-beijing-a", "image_id": "img-abcdef1234567890", "vpc_id": "vpc-abcdef1234567890", "subnet_id": "subnet-abcdef1234567890", "security_group_ids": [ "sg-abcdef1234567890" ], "status": "Running", "public_ip_address": "1.2.3.4", "private_ip_address": "10.0.0.1" } ``` ``` -------------------------------- ### Create EBS Snapshot Source: https://context7.com/volcengine/terraform-provider-volcenginecc/llms.txt This resource creates a snapshot of an existing EBS volume, serving as a backup. It requires the volume ID, snapshot name, and an optional description. Tags can be added to specify backup schedules or other metadata. ```hcl resource "volcenginecc_storageebs_snapshot" "data_backup" { volume_id = volcenginecc_storageebs_volume.data_volume.id snapshot_name = "data-snapshot-daily" description = "Daily backup snapshot" tags = [ { key = "schedule" value = "daily" } ] } ``` -------------------------------- ### Import HBase Instance using Terraform CLI Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/docs/resources/hbase_instance.md Demonstrates how to import an existing Volcenginecc HBase instance into your Terraform state. This command requires the Terraform CLI and the instance ID of the HBase instance you wish to import. The output will be the successful import of the resource into your Terraform state. ```shell terraform import volcenginecc_hbase_instance.example "instance_id" ``` -------------------------------- ### Create ECS Instance with Comprehensive Configuration (Terraform) Source: https://context7.com/volcengine/terraform-provider-volcenginecc/llms.txt This snippet demonstrates how to create a Volcengine Elastic Compute Service (ECS) instance with detailed configurations. It includes instance naming, type, image, network settings, storage, user data for initialization, and tags. Ensure the 'volcenginecc_vpc_vpc.main_vpc.vpc_id' and image/security group IDs are correctly specified. ```hcl resource "volcenginecc_ecs_instance" "application_server" { instance_name = "app-server-prod-01" description = "Application server for production workload" instance_type = "ecs.g2i.xlarge" image_id = "image-xyz123abc456" vpc_id = volcenginecc_vpc_vpc.main_vpc.vpc_id subnet_id = "subnet-abc123" security_group_ids = ["sg-firewall-web"] key_pair_name = "prod-keypair" # Storage configuration system_volume_type = "ESSD_PL0" system_volume_size = 100 # Network configuration primary_network_interface { subnet_id = "subnet-abc123" security_group_ids = ["sg-firewall-web", "sg-monitoring"] private_ip_address = "10.0.1.10" } # User data for initialization user_data = base64encode(<<-EOF #!/bin/bash yum update -y yum install -y docker systemctl start docker systemctl enable docker docker run -d -p 8080:8080 myapp:latest EOF ) project_name = "production" tags = [ { key = "role" value = "application" }, { key = "environment" value = "production" } ] } ``` -------------------------------- ### Import Existing ALB Resource Source: https://context7.com/volcengine/terraform-provider-volcenginecc/llms.txt Demonstrates how to import an existing ALB resource into Terraform state. This command is used when managing infrastructure that was created outside of Terraform. ```bash # terraform import volcenginecc_alb_load_balancer.imported alb-xyz123abc456 ``` -------------------------------- ### VPC Resource Management Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/docs/index.md Manage Virtual Private Cloud (VPC) resources, including creation and querying. ```APIDOC ## VPC Resource Management ### Description This section details the management of VPC resources, including creating a new VPC and querying existing VPCs using the `volcenginecc` Terraform provider. ### Method Resource Creation (POST), Data Source Query (GET) ### Endpoint N/A (Terraform resource/data source definition) ### Parameters #### Path Parameters None #### Query Parameters None #### Request Body (for resource creation) * **vpc_name** (String) - Required - The name of the VPC. * **description** (String) - Optional - A description for the VPC. * **cidr_block** (String) - Required - The CIDR block for the VPC. * **support_ipv_4_gateway** (Boolean) - Optional - Whether to support IPv4 gateway. * **enable_ipv_6** (Boolean) - Optional - Whether to enable IPv6. * **project_name** (String) - Optional - The name of the project. * **tags** (List of Objects) - Optional - Tags to associate with the VPC. * **key** (String) - Required - The key of the tag. * **value** (String) - Required - The value of the tag. #### Request Example (Resource Creation) ```terraform resource "volcenginecc_vpc_vpc" "VPCDemo" { vpc_name = "vpc-demo" description = "VpcDemo Example" cidr_block = "192.168.0.0/24" support_ipv_4_gateway = true enable_ipv_6 = false project_name = "default" tags = [ { key = "env" value = "test" } ] } ``` #### Request Example (Data Source Query) ```terraform data "volcenginecc_vpc_vpc" "VpcVpcDataSource" { id = volcenginecc_vpc_vpc.VPCDemo.id } ``` ### Response #### Success Response (200) * **id** (String) - The unique identifier of the VPC. * **vpc_name** (String) - The name of the VPC. * **description** (String) - The description of the VPC. * **cidr_block** (String) - The CIDR block of the VPC. * **support_ipv_4_gateway** (Boolean) - Indicates if IPv4 gateway is supported. * **enable_ipv_6** (Boolean) - Indicates if IPv6 is enabled. * **project_name** (String) - The name of the project. * **tags** (List of Objects) - Tags associated with the VPC. * **key** (String) - The key of the tag. * **value** (String) - The value of the tag. #### Response Example (Data Source Query) ```json { "id": "vpc-abcdef1234567890", "vpc_name": "vpc-demo", "description": "VpcDemo Example", "cidr_block": "192.168.0.0/24", "support_ipv_4_gateway": true, "enable_ipv_6": false, "project_name": "default", "tags": [ { "key": "env", "value": "test" } ] } ``` ``` -------------------------------- ### volcenginecc_filenas_instance Data Source Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/docs/data-sources/filenas_instance.md Provides information about Volcengine FileNAS instances, allowing you to retrieve details about existing instances based on their ID. ```APIDOC ## Data Source: volcenginecc_filenas_instance ### Description Data Source schema for Volcengine::FileNAS::Instance. Provides information about Volcengine FileNAS instances, allowing you to retrieve details about existing instances based on their ID. ### Method GET ### Endpoint /api/v1/filenas/instances/{id} ### Parameters #### Path Parameters - **id** (String) - Required - Uniquely identifies the FileNAS instance. #### Query Parameters None #### Request Body None ### Request Example ```json { "id": "f-xxxxxxxxxxxxxxxxx" } ``` ### Response #### Success Response (200) - **id** (String) - Uniquely identifies the resource. - **cache_performance** (Attributes) - 缓存型性能信息。 - **cache_bandwidth** (Number) - 预配置带宽,用于增加文件系统带宽。 - **capacity** (Attributes) - 文件系统容量。 - **total** (Number) - 文件系统可用总容量,单位为 GiB。 - **used** (Number) - 文件系统已使用容量,单位为 MiB。 - **charge_type** (String) - 计费类型,取值 PayAsYouGo,表示按量计费。 - **create_time** (String) - 创建时间 - **description** (String) - 描述信息。 - **file_system_id** (String) - 文件系统 ID。 - **file_system_name** (String) - 文件系统名称。 - **file_system_type** (String) - 文件系统类型。取值说明:Extreme:NAS 极速型;Capacity:NAS 容量型;Cache:NAS 缓存型。 - **project_name** (String) - 所属项目,默认值为 default 项目。 - **protocol_type** (String) - 文件系统协议类型。取值 NFS,表示 NFS 协议,常用于 Linux 客户端。 - **snapshot_count** (Number) - 快照数量 - **snapshot_id** (String) - 创建时使用的快照 ID。传入该参数后,将使用该快照新建文件系统。 - **status** (String) - 文件系统状态 - **storage_type** (String) - 存储类型,取值Standard,表示标准型。 - **tags** (Attributes Set) - 文件系统的标签信息 - **key** (String) - 标签键。 - **type** (String) - 标签类型。 - **value** (String) - 标签值。 - **update_time** (String) - 更新时间 - **zone_id** (String) - 可用区 ID。 - **zone_name** (String) - 可用区名称。 #### Response Example ```json { "id": "f-xxxxxxxxxxxxxxxxx", "cache_performance": { "cache_bandwidth": 100 }, "capacity": { "total": 1024, "used": 512 }, "charge_type": "PayAsYouGo", "create_time": "2023-01-01T10:00:00Z", "description": "My FileNAS instance", "file_system_id": "fs-xxxxxxxxxxxxxxxxx", "file_system_name": "my-filenas-instance", "file_system_type": "Capacity", "project_name": "default", "protocol_type": "NFS", "snapshot_count": 5, "snapshot_id": "snap-xxxxxxxxxxxxxxxxx", "status": "Active", "storage_type": "Standard", "tags": [ { "key": "environment", "type": "user", "value": "production" } ], "update_time": "2023-01-01T11:00:00Z", "zone_id": "cn-north-1a", "zone_name": "cn-north-1a" } ``` ``` -------------------------------- ### Create Volcengine NAT Gateway with SNAT and DNAT Source: https://context7.com/volcengine/terraform-provider-volcenginecc/llms.txt Configures a Volcengine NAT Gateway with SNAT and DNAT rules. This includes creating the NAT gateway itself, associating a NAT IP, defining an SNAT entry for private subnet internet access, and setting up a DNAT entry for incoming HTTPS traffic to a web server. ```hcl # Create NAT Gateway resource "volcenginecc_natgateway_ngw" "main_nat" { vpc_id = volcenginecc_vpc_vpc.main_vpc.vpc_id subnet_id = "subnet-nat-gateway" nat_gateway_name = "prod-nat-gateway" description = "NAT gateway for private subnet internet access" spec = "Medium" billing_type = "PostPaid" project_name = "production" tags = [ { key = "purpose" value = "internet-gateway" } ] } # Create NAT IP resource "volcenginecc_natgateway_nat_ip" "nat_ip_1" { nat_gateway_id = volcenginecc_natgateway_ngw.main_nat.id nat_ip_name = "nat-ip-1" description = "NAT IP for SNAT" } # Create SNAT entry resource "volcenginecc_natgateway_snatentry" "subnet_snat" { nat_gateway_id = volcenginecc_natgateway_ngw.main_nat.id subnet_id = "subnet-private-tier" nat_ip_id = volcenginecc_natgateway_nat_ip.nat_ip_1.id snat_entry_name = "private-subnet-snat" description = "SNAT for private subnet internet access" } # Create DNAT entry resource "volcenginecc_natgateway_dnatentry" "web_server_dnat" { nat_gateway_id = volcenginecc_natgateway_ngw.main_nat.id external_ip = "203.0.113.10" external_port = "443" internal_ip = "10.0.1.100" internal_port = "8443" protocol = "tcp" dnat_entry_name = "web-server-https-dnat" description = "DNAT for web server HTTPS traffic" } ``` -------------------------------- ### Volcenginecc Provider Configuration Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/README.md This section details how to configure the Volcenginecc provider, including authentication methods and optional settings. ```APIDOC ## Provider Configuration ### Description Configuration block for the Volcenginecc Terraform provider. ### Method Provider Configuration ### Endpoint N/A ### Parameters #### Path Parameters None #### Query Parameters None #### Request Body None ### Request Example ```terraform provider "volcenginecc" { access_key = "your ak" secret_key = "your sk" region = "cn-beijing" } ``` ### Response #### Success Response (200) Provider configuration is applied. #### Response Example N/A ### Optional Parameters - `access_key` (String) - The Access Key for Volcengine Provider. It must be provided, but it can also be sourced from the `VOLCENGINE_ACCESS_KEY` environment variable. - `secret_key` (String) - The Secret Key for Volcengine Provider. It must be provided, but it can also be sourced from the `VOLCENGINE_SECRET_KEY` environment variable. - `assume_role` (Attributes) - An `assume_role` block (documented below). Only one `assume_role` block may be in the configuration. - `customer_headers` (String) - CUSTOMER HEADERS for Volcengine Provider. The customer_headers field uses commas (,) to separate multiple headers, and colons (:) to separate each header key from its corresponding value. - `disable_ssl` (Boolean) - Disable SSL for Volcengine Provider. - `endpoints` (Attributes) - An `endpoints` block (documented below). Only one `endpoints` block may be in the configuration. - `proxy_url` (String) - PROXY URL for Volcengine Provider. - `region` (String) - The Region for Volcengine Provider. It must be provided, but it can also be sourced from the `VOLCENGINE_REGION` environment variable. ### Nested Schema for `assume_role` Required: - `assume_role_session_name` (String) - The session name to use when making the AssumeRole call. - `assume_role_trn` (String) - The TRN of the role to assume. - `duration_seconds` (Number) - The duration of the session when making the AssumeRole call. Its value ranges from 900 to 43200(seconds), and default is 3600 seconds. Optional: - `policy` (String) - A more restrictive policy when making the AssumeRole call ### Nested Schema for `endpoints` Optional: - `cloudcontrolapi` (String) - Use this to override the default Cloud Control API service endpoint URL - `sts` (String) - Use this to override the default STS service endpoint URL ``` -------------------------------- ### volcenginecc_iam_accesskeys Data Source Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/docs/data-sources/iam_accesskeys.md This data source allows you to query multiple IAM Access Keys. It returns a set of identifiers for the access keys. ```APIDOC ## Data Source: volcenginecc_iam_accesskeys ### Description Plural Data Source schema for Volcengine::IAM::Accesskey. This data source allows you to retrieve a list of access key identifiers. ### Method GET ### Endpoint This data source does not represent a direct API endpoint but rather a way to query resources managed by the provider. ### Parameters This data source does not have explicit parameters for querying. ### Request Example ```hcl data "volcenginecc_iam_accesskeys" "default" { } ``` ### Response #### Success Response - **id** (String) - Uniquely identifies the data source. - **ids** (Set of String) - Set of Resource Identifiers for the IAM Access Keys. #### Response Example ```json { "id": "some_unique_data_source_id", "ids": [ "accesskey_id_1", "accesskey_id_2" ] } ``` ``` -------------------------------- ### Create RDS MySQL Instance (Terraform) Source: https://context7.com/volcengine/terraform-provider-volcenginecc/llms.txt This snippet shows how to provision a high-availability (HA) RDS MySQL instance on Volcengine. It includes configurations for the database engine version, node specifications, multi-zone deployment, storage, network, charging type, and backup settings. Project name and tags are also set. ```hcl resource "volcenginecc_rdsmysql_instance" "primary_db" { db_engine_version = "MySQL_8_0" node_spec = "rds.mysql.g2.large" primary_zone_id = "cn-beijing-a" secondary_zone_id = "cn-beijing-b" instance_name = "prod-mysql-primary" db_instance_type = "HA" storage_space = 100 storage_type = "ESSD_PL0" vpc_id = volcenginecc_vpc_vpc.main_vpc.vpc_id subnet_id = "subnet-database-tier" charge_type = "PostPaid" lower_case_table_names = "1" backup_window { backup_time = "02:00Z-03:00Z" retention_period = 7 } project_name = "production" tags = [ { key = "database" value = "mysql" }, { key = "backup" value = "enabled" } ] } ``` -------------------------------- ### Create ALB HTTPS Listener Source: https://context7.com/volcengine/terraform-provider-volcenginecc/llms.txt Configures an HTTPS listener on port 443 for the 'web-alb'. It forwards traffic to the 'web-server-pool' and includes settings for certificate management, access control lists (ACLs), and description. ```hcl resource "volcenginecc_alb_listener" "https_listener" { load_balancer_id = volcenginecc_alb_load_balancer.web_alb.id listener_name = "https-listener-443" protocol = "HTTPS" port = 443 server_group_id = volcenginecc_alb_server_group.web_servers.id certificate_id = "cert-abc123xyz" acl_status = "on" acl_type = "white" acl_ids = ["acl-allowlist-123"] description = "HTTPS listener for web traffic" enabled = true tags = [ { key = "protocol" value = "https" } ] } ``` -------------------------------- ### Create EBS Volume Source: https://context7.com/volcengine/terraform-provider-volcenginecc/llms.txt This resource provisions an Elastic Block Store (EBS) volume for persistent storage. Key parameters include volume name, type (e.g., ESSD_PL1), size, zone ID, description, project name, and tags for organization and backup policies. ```hcl resource "volcenginecc_storageebs_volume" "data_volume" { volume_name = "app-data-volume" volume_type = "ESSD_PL1" size = 500 zone_id = "cn-beijing-a" description = "High-performance data volume for application" project_name = "production" tags = [ { key = "purpose" value = "application-data" }, { key = "backup" value = "daily" } ] } ``` -------------------------------- ### volcenginecc_bmq_instances Data Source Source: https://github.com/volcengine/terraform-provider-volcenginecc/blob/main/docs/data-sources/bmq_instances.md Provides a way to query multiple Message Queue (BMQ) instances. This data source can be used to retrieve a list of instance IDs and other relevant information for existing BMQ instances. ```APIDOC ## Read-Only Schema ### `id` (String) Uniquely identifies the data source. ### `ids` (Set of String) Set of Resource Identifiers. ``` -------------------------------- ### Enable Volcengine Terraform Provider Debugging Source: https://context7.com/volcengine/terraform-provider-volcenginecc/llms.txt Provides commands and environment variables to enable detailed debug logging for the Volcengine Terraform provider. This includes setting `TF_LOG` and `VOLCENGINE_LOG_LEVEL` to 'DEBUG', running Terraform with detailed output, and filtering logs to inspect Cloud Control API operations. It also shows how to verify provider configuration and test connectivity. ```bash # Enable Terraform debug logging export TF_LOG=DEBUG export TF_LOG_PATH=./terraform-debug.log # Enable provider-specific logging export VOLCENGINE_LOG_LEVEL=debug # Run Terraform with detailed output terraform apply -auto-approve # Check Cloud Control API operations cat terraform-debug.log | grep "cloudcontrol" # Verify provider configuration terraform console > provider::volcenginecc::region "cn-beijing" # Test connectivity cat > test.tf <