-
Notifications
You must be signed in to change notification settings - Fork 59
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
[BUG] With version 2.3.0 of the provider, the ressource opensearch_channel_configuration cannot be applied when assuming an iam role in the provider #200
Labels
bug
Something isn't working
Comments
The following terraform code works for me
|
Can you try using an AWS SNS channel instead of a webhook? |
The following works for me
|
getsaurabh02
moved this from 🆕 New
to Later (6 months plus)
in Engineering Effectiveness Board
Jul 18, 2024
Thanks @rblcoder, closing this issue @Jaewongtongsoup please feel-free to re-open if required. |
github-project-automation
bot
moved this from Backlog
to ✅ Done
in Engineering Effectiveness Board
Sep 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the bug?
With version 2.3.0 of the provider, the ressource opensearch_channel_configuration cannot be applied when assuming an iam role in the provider like so :
Do you have any screenshots?
provider.terraform-provider-opensearch_v2.3.0: Response contains error diagnostic: diagnostic_severity=ERROR tf_proto_version=5.4 tf_provider_addr=provider tf_resource_type=opensearch_channel_configuration @module=sdk.proto diagnostic_detail= tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/[email protected]/tfprotov5/internal/diag/diagnostics.go:58 diagnostic_summary="HTTP 403 Forbidden: Permission denied. Please ensure that the correct credentials are being used to access the cluster." tf_req_id=4c4f9019-ad7d-e488-f5e9-008d96464823 timestamp=2024-06-20T17:46:03.247Z
It works perfectly when I force version 2.2.0 of the provider.
Other ressources that also uses this provider configs with version 2.3.0 doesnt seems to be affected and works perfectly like :
The text was updated successfully, but these errors were encountered: