not yet implemented: ForExpression
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
What happened?
Some AWS examples fail to render to Java with not yet implemented: ForExpression, looks like some omission in programgen.
Example
HCL source:
resource "aws_lb" "test" {
name = "test-lb-tf"
internal = false
load_balancer_type = "network"
subnets = [for subnet in aws_subnet.public : subnet.id]
enable_deletion_protection = true
tags = {
Environment = "production"
}
}
Similar to https://github.com/pulumi/pulumi/issues/19718
Output of pulumi about
pulumi v3.171.0
terraform converter 1.2.0
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the programgen handling for Terraform ForExpression and reproduce the failure with the supplied AWS load-balancer HCL example. Trace the Terraform converter's Java-generation path and identify how similar expressions are handled. Done means the example renders to Java without the "not yet implemented: ForExpression" error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java, terraform
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100