Discrepancy in Lambda Types Between Terraform Provider and FusionAuth UI/API

[sanjesh1000]

I hope this message finds you well. I am currently working on managing FusionAuth using Terraform, and I have identified a couple of discrepancies that I would like to bring to your attention:

1. Discrepancy in Available Lambda Types
   In the FusionAuth UI and API documentation, I have observed that there are 25 Lambda types available. However, when using the Terraform provider, only 20 Lambda types are supported. The Terraform provider only includes the following types:

"JWTPopulate"
"OpenIDReconcile"
"SAMLv2Reconcile"
"SAMLv2Populate"
"AppleReconcile"
"ExternalJWTReconcile"
"FacebookReconcile"
"GoogleReconcile"
"HYPRReconcile"
"TwitterReconcile"
"LDAPConnectorReconcile"
"LinkedInReconcile"
"EpicGamesReconcile"
"NintendoReconcile"
"SonyPSNReconcile"
"SteamReconcile"
"TwitchReconcile"
"XboxReconcile"
"SelfServiceRegistrationValidation"
"ClientCredentialsJWTPopulate"
This list is missing 5 Lambda types compared to what is available in the FusionAuth UI and API. Could you confirm if this is an issue with the Terraform provider, or if there are plans to include the missing Lambda types in future updates?

** Naming Style Inconsistency**
Additionally, I noticed that there is a difference in the naming style of Lambda types between the FusionAuth UI/API and the Terraform provider. In Terraform, the names are more "snake_case" (e.g., "JWTPopulate"), whereas in the FusionAuth UI/API, they follow a "Title Case" or different style.

This difference in naming convention makes it difficult to maintain consistency between the two environments, especially when working with automation tools. Could you clarify if the naming convention difference is intentional? If not, is there a possibility to standardize the naming styles between the UI/API and Terraform?

[mrudatsprint]

The missing Lambda types are:

• SCIMServerGroupRequestConverter
• SCIMServerGroupResponseConverter
• SCIMServerUserRequestConverter
• SCIMServerUserResponseConverter
• UserInfoPopulate
• LoginValidation

[mrudatsprint]

@sanjesh1000 The naming convention follows the format of the type request parameter.

[daethnir]

#303 would fix LoginValidation.

[daethnir]

If my fix in #303 works then I'll happily add the others, but I'd need verification it's sufficient first.

[sareh]

I'm also interested in this fix. Thanks for the PR, @daethnir. I have opened a support request with the FusionAuth team regarding this discrepancy, so hopefully someone should review this ticket and your PR soon.