fix(teo): [134409549]Optimize the handling of empty return results in the read function of tencentcloud_teo_l7_acc_rule_v2. (#4147)

* docs(teo): update tencentcloud_teo_l7_acc_rule_v2 resource documentation

* fix(teo): revert field descriptions and fix read function nil check

- Restore original field descriptions in resource_tc_teo_l7_acc_rule_extension.go
- Fix Read function to check for empty Rules array: if respData == nil || len(respData.Rules) == 0
- Restore website documentation to match original descriptions
- Move openspec change from archive back to active state with updated tasks

* docs(teo): archive openspec change for teo_l7_acc_rule_v2

* fix(teo): normalize openspec proposal and update changelog for l7_acc_rule_v2 Read fix

- Update .changelog/4147.txt to reflect the actual bug fix (Read function
  handling empty Rules array)
- Move openspec change from archive back to active state
- Normalize openspec proposal to accurately describe the branch change

* docs(teo): update teo l7 acc rule v2 openspec archive

* fix: modify md

* fix: modify md

---------

Co-authored-by: CodeBuddy <codebuddy@tencentcloud.com>
Co-authored-by: Terraform Provider <terraform@tencentcloud.com>
Co-authored-by: arunma <arunma@tencent.com>

Author: 4 people

.changelog/4147.txt

@@ -0,0 +1,3 @@
+```release-note:bug
+resource/tencentcloud_teo_l7_acc_rule_v2: fix Read function to handle empty Rules array from API response
+```

openspec/changes/archive/2026-05-26-fix-teo-l7-acc-rule-v2-empty-rules-array/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-04-28

openspec/changes/archive/2026-05-26-fix-teo-l7-acc-rule-v2-empty-rules-array/design.md

@@ -0,0 +1,20 @@
+## Context
+
+The `tencentcloud_teo_l7_acc_rule_v2` resource manages individual TEO L7 acceleration rules. The Read function previously only checked `if respData == nil` to determine if the resource was deleted. However, the DescribeL7AccRules API can return a valid response with an empty `Rules` array when the rule no longer exists, which was not handled.
+
+## Goals / Non-Goals
+
+**Goals:**
+- Fix Read function to handle empty Rules array from API response
+- Ensure resource is properly marked as deleted when API returns empty Rules
+
+**Non-Goals:**
+- Changing any other resource behavior
+
+## Decisions
+
+1. **Fix Read function nil check**: Change `if respData == nil {` to `if respData == nil || len(respData.Rules) == 0 {` to properly handle the case where the API returns a response with an empty Rules array (resource deleted).
+
+## Risks / Trade-offs
+
+- No risks. This is a purely defensive fix that handles an edge case in the API response.

openspec/changes/archive/2026-05-26-fix-teo-l7-acc-rule-v2-empty-rules-array/proposal.md

@@ -0,0 +1,16 @@
+## Why
+
+The `tencentcloud_teo_l7_acc_rule_v2` resource's Read function only checked if `respData == nil` before marking the resource as deleted. However, the API can also return a valid response with an empty `Rules` array when the rule has been deleted. This caused the Read function to proceed with an empty array and potentially panic or produce incorrect state.
+
+## What Changes
+
+- Fix Read function: change `if respData == nil` to `if respData == nil || len(respData.Rules) == 0` to handle empty Rules array
+
+## Capabilities
+
+### Modified Capabilities
+- `l7-acc-rule-v2-read-fix`: Fix the Read function to properly detect deleted resources when the API returns an empty Rules array instead of nil.
+
+## Impact
+
+- `tencentcloud/services/teo/resource_tc_teo_l7_acc_rule_v2.go`: Fix Read function nil check to also handle empty Rules array

openspec/changes/archive/2026-05-26-fix-teo-l7-acc-rule-v2-empty-rules-array/specs/rule-ids-output/spec.md

@@ -0,0 +1,13 @@
+## MODIFIED Requirements
+
+### Requirement: Read function handles empty Rules array
+
+The `tencentcloud_teo_l7_acc_rule_v2` resource's Read function SHALL handle both nil response and empty Rules array as indicators that the resource has been deleted.
+
+#### Scenario: API returns empty Rules array
+- **WHEN** the DescribeL7AccRules API returns a response with an empty `Rules` array
+- **THEN** the Read function SHALL mark the resource as deleted by calling `d.SetId("")`
+
+#### Scenario: API returns nil response
+- **WHEN** the DescribeL7AccRules API returns a nil response
+- **THEN** the Read function SHALL mark the resource as deleted by calling `d.SetId("")`

openspec/changes/archive/2026-05-26-fix-teo-l7-acc-rule-v2-empty-rules-array/tasks.md

@@ -0,0 +1,3 @@
+## 1. 修复 Read 函数
+
+- [x] 1.1 将 Read 函数中 `if respData == nil {` 修改为 `if respData == nil || len(respData.Rules) == 0 {`

openspec/specs/rule-ids-output/spec.md

@@ -35,3 +35,15 @@ The `actions.name` field description SHALL list all valid action names matching
 #### Scenario: name description matches SDK
 - **WHEN** a user reads the `actions.name` field description
 - **THEN** it SHALL include all supported actions from `RuleEngineAction.Name` in the SDK, including `SetContentIdentifier`, `Vary`, `ContentCompression`, and `OriginAuthentication`
+
+### Requirement: Read function handles empty Rules array
+
+The `tencentcloud_teo_l7_acc_rule_v2` resource's Read function SHALL handle both nil response and empty Rules array as indicators that the resource has been deleted.
+
+#### Scenario: API returns empty Rules array
+- **WHEN** the DescribeL7AccRules API returns a response with an empty `Rules` array
+- **THEN** the Read function SHALL mark the resource as deleted by calling `d.SetId("")`
+
+#### Scenario: API returns nil response
+- **WHEN** the DescribeL7AccRules API returns a nil response
+- **THEN** the Read function SHALL mark the resource as deleted by calling `d.SetId("")`

tencentcloud/services/teo/resource_tc_teo_l7_acc_rule_v2.go

@@ -148,7 +148,7 @@ func ResourceTencentCloudTeoL7AccRuleV2Read(d *schema.ResourceData, meta interfa
 		return err
 	}
 
-	if respData == nil {
+	if respData == nil || len(respData.Rules) == 0 {
 		d.SetId("")
 		log.Printf("[WARN]%s resource `teo_l7_acc_rule` [%s] not found, please check if it has been deleted.\n", logId, d.Id())
 		return nil