Null computed ListAttribute when data source is read at apply time

[marshallford]

Hello 👋🏼 I apologize if this is a bug in my provider and not the plugin framework. This has been a head scratcher, so I thought I would open an issue. Thank you.

Module version

github.com/hashicorp/terraform-plugin-framework v1.13.0

Relevant provider source code

"artifact_queries": schema.MapNestedAttribute{
	Optional:            true,
	NestedObject: schema.NestedAttributeObject{
		Attributes: map[string]schema.Attribute{
			"jq_filter": schema.StringAttribute{
				Required:            true,
				Validators: []validator.String{
					stringIsJQFilter(),
				},
			},
			"results": schema.ListAttribute{
				Computed:            true,
				ElementType:         jsontypes.NormalizedType{},
			},
		},
	},
},

Terraform Configuration Files

See example here: marshallford/terraform-provider-ansible#79

Debug Output

https://gist.github.com/marshallford/38c159bd2ab5f7bb11119232bb717d8e

Expected Behavior

The data source attribute is considered "unknown" until it has been read. After the data source has been read the normal resource graph ordering should allow the data source attribute to be passed to other resources/outputs/etc.

Actual Behavior

The ListAttribute is not shown in the Terraform plan output (with (known after apply)) and Terraform evaluates the attribute as null before the data source has a chance to be read. It is almost as if there is a difference in behavior between a ListAttribute within a SingleNestedAttribute and a ListAttribute within a MapNestedAttribute.

Steps to Reproduce

1. terraform init
2. terraform plan

References

marshallford/terraform-provider-ansible#79