Closed colinhuckstep closed 2 months ago
@colinhuckstep, thank you for the clear bug report. We have noted this internally and will update you on any progress.
This fix will be included in the next provider release.
This fix was included in the v0.15.0 release - https://registry.terraform.io/providers/pingidentity/pingfederate/0.15.0
Community Note
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
PingFederate Terraform provider Version
0.13.0
PingFederate Version
11.3.5
Terraform Version
v1.9.3
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Debug Output
Please provide your debug output with
TF_LOG=DEBUG
enabled on yourterraform plan
orterraform apply
. Please provide a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.Panic Output
If Terraform produced a panic, please provide your debug output from the GO panic
Expected Behavior
Application Policies Created/Updated without error.
Actual Behavior
The policy gets created however the validation fails resulting in the below error. It seems like there's an issue with checking the type when creating an LDAP Attribute Source on and Authentication Policy Contract.
│ Error: Provider produced inconsistent result after apply │ │ When applying changes to pingfederate_authentication_policies.authenticationPolicies, provider │ "provider[\"registry.terraform.io/pingidentity/pingfederate\"]" produced an unexpected new value: │ .authn_selection_trees[0].root_node.children[0].children[0].children[1].children[0].children[1].action.apc_mapping_policy_action.attribute_mapping.attribute_sources: │ planned set element │ cty.ObjectVal(map[string]cty.Value{"custom_attribute_source":cty.NullVal(cty.Object(map[string]cty.Type{"attribute_contract_fulfillment":cty.Map(cty.Object(map[string]cty.Type{"source":cty.Object(map[string]cty.Type{"id":cty.String, │ "type":cty.String}), "value":cty.String})), "data_store_ref":cty.Object(map[string]cty.Type{"id":cty.String}), │ "description":cty.String, "filter_fields":cty.Set(cty.Object(map[string]cty.Type{"name":cty.String, │ "value":cty.String})), "id":cty.String, "type":cty.String})), │ "jdbc_attribute_source":cty.NullVal(cty.Object(map[string]cty.Type{"attribute_contract_fulfillment":cty.Map(cty.Object(map[string]cty.Type{"source":cty.Object(map[string]cty.Type{"id":cty.String, │ "type":cty.String}), "value":cty.String})), "column_names":cty.List(cty.String), │ "data_store_ref":cty.Object(map[string]cty.Type{"id":cty.String}), "description":cty.String, "filter":cty.String, │ "id":cty.String, "schema":cty.String, "table":cty.String, "type":cty.String})), │ "ldap_attribute_source":cty.ObjectVal(map[string]cty.Value{"attribute_contract_fulfillment":cty.UnknownVal(cty.Map(cty.Object(map[string]cty.Type{"source":cty.Object(map[string]cty.Type{"id":cty.String, │ "type":cty.String}), "value":cty.String}))), │ "base_dn":cty.StringVal("OU=Users,OU=Accounts,DC=internal,DC=domain,DC=net"), │ "binary_attribute_settings":cty.NullVal(cty.Map(cty.Object(map[string]cty.Type{"binary_encoding":cty.String}))), │ "data_store_ref":cty.ObjectVal(map[string]cty.Value{"id":cty.StringVal("LDAP-INTERNAL")}), │ "description":cty.StringVal("Employee AD"), "id":cty.StringVal("EmployeeAD"), │ "member_of_nested_group":cty.False, "search_attributes":cty.SetVal([]cty.Value{cty.StringVal("Subject DN"), │ cty.StringVal("mail"), cty.StringVal("memberOf")}), │ "search_filter":cty.StringVal("sAMAccountName=${ad.InternalADHTMLAdapter.username}"), │ "search_scope":cty.StringVal("SUBTREE"), "type":cty.StringVal("LDAP")})}) does not correlate with any element in │ actual. │ │ This is a bug in the provider, which should be reported in the provider's own issue tracker.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply