Open Hawxy opened 2 months ago
Hi @Hawxy - thank you for filing this issue.
To make sure I'm understanding you correctly - what you're seeing is that despite not specifying isSignupEnabled
on your OrganizationConnection
, you are getting an error from the auth0 API that you can't use this field.
This is an auth0 api error; it's not coming from Pulumi or Terraform, which makes me inclined to think this is an upstream bug, although I can't see an open issue regarding this there.
In order to help us help you more effectively, could you do the following for us:
~provide us with a complete minimal repro that shows this behavior~
~send us a Gist with the output of PULUMI_DEBUG_GRPC=logs.json pulumi up
~
update: I have a repro, using a combination of your code and the documentation. I have also verified that this does not happen with an equivalent Terraform program.
This is a bug on our end. We will continue to investigate.
I just ran into this exact problem as well
Describe what happened
The terraform provider recently added a few new fields to the organization connection configuration, namely
is_signup_enabled
&show_as_button
. However,is_signup_enabled
should only be used with database connections as the endpoint returns 400 with any other connection type. If the property isn't added to the options then I would expect it not to be sent, but this doesn't appear to be the case given the exception being returned. I'm not sure if this an issue on the bridge side or the terraform provider itself.Sample program
Log output
Affected Resource(s)
OrganizationConnection
Output of
pulumi about
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).