Add ability to opt out of singularizing words on properties

[zbuchheit]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Currently if I have an array property the bridge will singularize it. It would be nice to be able to opt out of that functionality.

For example, if I have a field like ConfigValuesArgs array it would be converted to ConfigValueArgs

Affected area/feature

TF Bridge

[iwahbe]

@zbuchheit Do you know if the customer is interested in disabling this globally, or for specific fields or resources.

---

If they want to disable all type aware case manipulation, I think they can do this:

tfbridge.MustTraverseProperties(&prov, "disable-type-aware-naming",
        func(info tfbridge.PropertyVisitInfo) (tfbridge.PropertyVisitResult, error) {
            p := info.SchemaPath()
            step, ok := p[len(p)-1].(walk.GetAttrStep)
            if !ok {
                return tfbridge.PropertyVisitResult{}, nil
            }

            sInfo := info.SchemaInfo()
            if sInfo.Name != "" {
                return tfbridge.PropertyVisitResult{}, nil
            }
            sInfo.Name = tfbridge.TerraformToPulumiNameV2(step.Name, nil, nil)
            return tfbridge.PropertyVisitResult{HasEffect: true}, nil
        })

[zbuchheit]

I believe they would be interested in disabling this globally, but mainly the interest right now is for specific fields/resources.

They tried the above, but ended up with bunch of overriding non-existent field errors