-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using the converter renders less informative Java var names #88
Comments
Yeh we need to make use of __logicalName to not change resource names in conversion. |
Looks like the same problem is affecting not just Java, but python, node and Go. I had a build problem that was masking that. But now it's uncovered. |
This is because the converter is using "Resource" as a suffix to make the resource names unique rather than using the type of the resource. Should be a fairly easy fix. |
I think this looks done as of this morning! |
@Frassle, what's involved to fix this? Is this a quick fix that you or @Zaid-Ajaj could pick up? |
pulumi/pulumi-azure#1377 specifically does not have this problem anymore. After it picked up 1.0.13 in pulumi/pulumi-azure@f9d3f3b so I think 1.0.13 must contain a fix. |
#107 would have fixed this. There's a couple of outstanding questions from that implementation though. Firstly, if variables conflict (i.e. two terraform blocks both called "example" but with different type) should we use the type name on all of them, or should the first be allowed to claim just "example"? Secondly, should we be suffixing with the type always, not just when there's name conflicts? Obviously if we answer yes to the second question the first question is redundant. |
It's aesthetics... I could go either way. I like exampleUser, exampleGroup personally better than example, exampleGroup but it does not matter all that much. |
Hello!
Issue details
This feels like a regression in the quality of the generated programs when introducing the converter into the pipeline.
Original PR where this is discovered: pulumi/pulumi-azuread#484
All variables are held equal during the comparison, the change is just introducing the
pulumi convert
plus the converter at 1.0.11 version into the pipeline.Example HCL:
Java rendering without the converter:
Java rendering with the converter:
Affected area/feature
The text was updated successfully, but these errors were encountered: