Skip to content

Commit fb9f3e6

Browse files
joelanfordclaude
andcommitted
🐛 e2e: don't pre-populate clusterObjectSetName in scenario context
The clusterObjectSetName was unconditionally set to a pre-generated value for every scenario in CreateScenarioContext, causing cleanup to attempt deleting a clusterobjectset resource even when the CRD doesn't exist (non-experimental suites). Now it starts empty and only gets set when a ClusterObjectSet is actually applied during the scenario. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 2b2669f commit fb9f3e6

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

test/e2e/steps/hooks.go

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,6 @@ func CreateScenarioContext(ctx context.Context, sc *godog.Scenario) (context.Con
166166
id: sc.Id,
167167
namespace: fmt.Sprintf("ns-%s", sc.Id),
168168
clusterExtensionName: fmt.Sprintf("ce-%s", sc.Id),
169-
clusterObjectSetName: fmt.Sprintf("cos-%s", sc.Id),
170169
leaderPods: make(map[string]string),
171170
}
172171
return context.WithValue(ctx, scenarioContextKey, scCtx), nil

0 commit comments

Comments
 (0)