You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 76a8ca4
Browse filesBrowse the repository at this point in the historyBrowse files
test: pin parameter, preset and tag values that flow from resources (#223)
Pins the parameter, preset, and tag values that flow from `resource`
blocks, ahead of #221 (which evaluates only the parameter/preset/tag
closure via coder/trivy#74). Everything passes on `main`, where nothing
is pruned, so a failure after rebasing #221 means pruning dropped a
resource a target depends on.
- `testdata/resourceclosure`: the fixture from #221 plus conditional,
`try()`, expression index, `option` and `dynamic "option"` blocks,
`count` on a target, a data-source intermediary, tag -> resource ->
parameter, preset `prebuilds`, and a local module.
- `testdata/resourceclosurejson`: a `.tf.json` template with two
resources in one expression. This currently fails against the #221 pin
(second resource pruned, default unknown); see the [comment on
coder/trivy#74](coder/trivy#74 (comment)).
- `testdata/diskaccess`: revives #85. `file()` on an in-tree path is
read; a path escaping the template root is unknown and flags the option
as invalid. Not closure-related, but a cheap guard that resource pruning
does not disturb function evaluation against the template fs.
- `testdata/chain`: revives #164. Pins two-hop count chaining: a
parameter count-gated on a count-gated parameter's `[0].value` is
silently dropped today because its count is evaluated before the input
flows in. The vector asserts current behavior and the comment says how
to flip it once fixed.
Prepared with Coder Agents assistance.
0 commit comments