docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "Evaluates how the solution uses @pulumi/pulumi provider data-source calls to fetch region details. Checks focus on invoking provider tokens with correct inputs, applying shared InvokeOptions, and combining results without losing Pulumi dependency/secret tracking.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Zone invoke",
"description": "Uses pulumi.runtime.invoke or pulumi.runtime.invokeOutput with the supplied zoneDataSourceToken and region argument to retrieve availability zones instead of hardcoded values.",
"max_score": 30
},
{
"name": "Image invoke",
"description": "Calls pulumi.runtime.invoke or pulumi.runtime.invokeOutput with imageDataSourceToken plus os/arch filters to obtain an image identifier, rather than fabricating the value.",
"max_score": 30
},
{
"name": "Shared options",
"description": "Builds a single pulumi.InvokeOptions object from the provided provider/parent/version inputs and passes it into both provider calls so they run under the same configuration.",
"max_score": 20
},
{
"name": "Output wiring",
"description": "Combines invoke results using pulumi.output/pulumi.all or invokeOutput so the returned shape preserves Pulumi Output semantics (dependencies and secrets) rather than converting to plain values prematurely.",
"max_score": 20
}
]
}