Teemu Matilainen
Teemu Matilainen
Thanks for the review! > I think we should only use the config unless there is a compelling argument. My use case was actually to dynamically ignore some environment variables...
Seems that the token is not stored after #298 (#287). Works after configuring a header for it with the `vouch.headers.idtoken`.
> Can you please post a working config here? The example config for Okta seems correct (except you have to drop `default/` part from the URLs unless using [API Access...
Setting an attribute to `null` is the same as not setting it at all, i.e. using the default value specified in the provider. So I don't think that only explains...
> Is there perhaps a workaround that allows use of `okta_policy_rule_signon` resources until this is fixed though? Can't test it now, but ignoring the attribute should work. Something like: ```terraform...
> Can't test it now, but ignoring the attribute should work And if it doesn't work in initial creation of the resource, at least by creating the rule manually and...
@monde while the problem with priority bug is real and annoying, IMHO the main issue here is the `identityProvider` attribute (as stated in the subject). To my understanding it's behind...
Are there any progress on this? Unfortunately the aforementioned 3rd party provider seems abandoned and hasn't had any updates for a couple of months, and [is even broken](https://github.com/gpsinsight/terraform-provider-fusionauth/issues/144) with the...
Generating the configuration for each and every Terraform module in a repository worked fine, until: > `The property '#/updates' had more items than the allowed 200` No idea how to...
I think this is related to (at least) #192 and #1541. The issue is not limited to the token, but also e.g. dynamic `address` attribute verification fails in some cases....