docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "Evaluates whether the solution uses Pulumi's stack-wide resource and invoke transformations to propagate default tags while respecting opt-outs. Confirms aliasing preserves resource identity when renameFrom is provided.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Stack transform",
"description": "Registers a stack-level resource transformation (e.g., via pulumi.runtime.registerStackTransformation or ResourceOptions.transformations) so every created resource passes through the tag/alias logic.",
"max_score": 25
},
{
"name": "Tag merge",
"description": "Transformation merges provided default tags into resource args without overwriting explicit tags and respects the skip list when deciding whether to modify a resource.",
"max_score": 20
},
{
"name": "Invoke transform",
"description": "Uses the invoke transformation hook (such as pulumi.runtime.registerInvokeTransform or InvokeOptions.transforms) to inject the default tag block into data-source call arguments while allowing caller overrides.",
"max_score": 20
},
{
"name": "Rename alias",
"description": "Configures ResourceOptions.aliases or equivalent to include the previous name when renameFrom is provided so updates reuse the existing resource instead of forcing replacement.",
"max_score": 20
},
{
"name": "Opt-out handling",
"description": "Transformation logic cleanly skips resources whose names appear in the skip list, ensuring no extra tags or aliases are added to those resources.",
"max_score": 15
}
]
}