-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin crashing for okta_inline_hook headers #1169
Comments
Thanks @nisargpansuria I can definitely see the logical flaw causing this panic https://github.com/okta/terraform-provider-okta/blob/master/okta/resource_okta_inline_hooks.go#L232-L244 if you have an empty resource "okta_inline_hook" "example" {
name = "example"
version = "1.0.0"
type = "com.okta.oauth2.tokens.transform"
channel = {
version = "1.0.0"
uri = "https://example.com/test"
method = "POST"
}
auth = {
key = "Authorization"
type = "HEADER"
value = "secret"
}
} |
@monde Yes, auth property was empty. When I added a dummy auth header with auth = { .. }, it let me set custom headers now from terraform (this exception is gone). So for now to bypass this exception I will need to set something in using auth = { .. } even though I am not using it, and use headers { .. } as I intended. This seems like a logical flaw in this provider. Terraform and Okta console is behaving differently. On the Okta console, the authentication field is not required to set custom headers on inline hook. |
Thank for the feedback @nisargpansuria . I'll label this a bug given the inconsistency in behavior you are describing and keep this issue open to address. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Getting this error when I try to add headers on okta_inline_hook.
Terraform resource:
Error on terraform apply:
The text was updated successfully, but these errors were encountered: