Fix dynamic for_each error for archs#67
Open
wlynch wants to merge 1 commit intochainguard-dev:mainfrom
Open
Conversation
```
Error: Invalid for_each argument
on .terraform/modules/base/main.tf line 55, in resource "cosign_attest" "this":
55: for_each = var.skip_attest ? [] : local.archs
├────────────────
│ local.archs is a set of dynamic, known only after apply
│ var.skip_attest is false
```
We can't derive this easily from the build output, even though it's the right thing to do.
This isn't an optimal solution, but this moves the arch value to a var, which then requires
that the archs must match the built archs else it will error on signing. I don't particularly
like this, but I don't know how else we can do this within only terraform without trying to determin
this based on computed dynamic outputs. :(
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We can't derive this easily from the build output, even though it's the right thing to do.
This isn't an optimal solution, but this moves the arch value to a var, which then requires that the archs must match the built archs else it will error on signing. I don't particularly like this, but I don't know how else we can do this within only terraform without trying to determin this based on computed dynamic outputs. :(