Open davide-talesco opened 2 years ago
I have a feeling this is due to an awkward default value to empty string being set in the upstream terraform resource schema (ie check name_id_policy_format here and the same happens to all other properties failing validation) but I do not quite understand why the terraform provider does not fail in the same way. I am willing to help open a PR to fix the issue if anyone can explain the above behaviour.
@jkodroff Any ideas on this?
@lblackstone any idea about this?
anyone looking at this?
@stack72 Any ideas?
At a glance, this may be similar to https://github.com/pulumi/pulumi-terraform-bridge/issues/577.
The provider is already forked, so I suggest that we remove the default value on the fork and see if it resolves the problem. If that works, create an issue in the Bridge that details the issue and link back to the bridge issue in the forked TF provider so we know when we can put the default back. (We want as little divergence from the original TF provider as possible.)
What happened?
Creating a basic saml identity provider with latest version of pulumi keycloak provider fails with a bunch of validation errors, while the same terraform template works as expected.
Also the example usage in nodejs sdk does not work for the same reason
Steps to reproduce
The below pulumi code fails with validation errors:
while its analogous terraform template using keycloak terraform provider works as expected
I have a feeling this is due to an awkward default value to empty string being set in the upstream terraform resource schema (ie check name_id_policy_format here and the same happens to all other properties failing validation) but I do not quite understand why the terraform provider does not fail in the same way. I am willing to help open a PR to fix the issue if anyone can explain the above behaviour.
Regards, Davide
Expected Behavior
The saml identity provider is created succesfully
Actual Behavior
The resource creation fails
Versions used
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).