Closed rjhornsby closed 1 year ago
Looks like there's a deeper issue with the provider. I can create resources just fine. However, if I do tf-plan
immediately after, it shows wanting to change the onelogin_saml_apps
resource and other AWS things chained to it. Doing tf-apply
at this point leads to the crash.
That is to say, it isn't required to create resources with the provider, change the TF code and then try to apply those changes. The same TF code that just created a onelogin_saml_apps
resource will show a delta and crash the OL provider.
We are in the process of standardizing our SDKs by using OpenAPI specifications. I have an OpenAPI generated terraform-provider-onelogin in prerelease if you would like t try it out. https://github.com/onelogin/terraform-provider-onelogin/tree/openapi
This bug no longer applies with the uncoupling of the onelogin go SDK from the terraform provider. See also onelogin/onelogin-go-sdk#63.
It's possible - likely even - that I've done something wrong in my TF code, but the output of the plugin crash specifically asks for a bug report.
The scenario is that I'm trying to set up a
onelogin_saml_apps
for AWS (connector id30319
). I imported the hand-configured saml app from OL, and then went to resolve the differences in my TF code to make it match.tf-plan
runs fine, but it still shows some differences. The plugin crash happens when I try totf-apply
Happy to provide more info, just not sure what else might be relevant/helpful.