You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation, there seems to be a bug related to the evaluation of the master_user_options field when the master_user_arn is set to a non-null string. This results in master_user_arn being incorrectly evaluated to null.
My understanding is that if master_user_options.value.master_user_arn has a value the try will evaluate to true making the outcome of the ternary expression null
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days
Description
In the current implementation, there seems to be a bug related to the evaluation of the
master_user_options
field when themaster_user_arn
is set to a non-null string. This results inmaster_user_arn
being incorrectly evaluated to null.Versions
Module version [Required]:
1.1.2
Terraform version:
1.6.6
Provider version(s):
Reproduction Code [Required]
Steps to reproduce the behavior:
Run terraform plan
Expected behavior
When
var.advanced_security_options.master_user_options.master_user_arn
is set, we should see that the arn is passed to the resourceActual behavior
Running plan for the above code shows that no
master_user_options
are configured as part ofaws_opensearch_domain
. See resource referenceAdditional context
Looking at the module I believe the issue is in this line in main.tf
My understanding is that if
master_user_options.value.master_user_arn
has a value the try will evaluate totrue
making the outcome of the ternary expressionnull
The text was updated successfully, but these errors were encountered: