Empty list with azurerm_public_ips without filters

[nerddtvg]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform v1.0.7
on windows_amd64
+ provider registry.terraform.io/hashicorp/azurerm v2.76.0
+ provider registry.terraform.io/hashicorp/kubernetes v2.5.0

Affected Resource(s)

• azurerm_public_ips

Terraform Configuration Files

data "azurerm_public_ips" "ips" {
  resource_group_name = "resource-group-name"
}

Debug Output

I do not have sanitized debug output I can provide. If needed, I will attempt to recreate this in a private subscription.

Expected Behaviour

With no filters (attached, name_prefix, or allocation_type), I would have expected all public IPs inside that resource group to be listed. All of these filters are listed as optional and no error is thrown.

Actual Behaviour

The public_ips list is empty.

Steps to Reproduce

1. Create resource group
2. Create one or more public IPs
3. Add the data source to Terraform
4. Run terraform refresh
5. Check state file to see the data source is empty
6. Change the data source to include attached = true
7. Refresh again
8. Verify the state file has IPs

Source of Issue

terraform-provider-azurerm/internal/services/network/public_ips_data_source.go

Lines 102 to 105 in ad46e90

	attachedOnly := d.Get("attached").(bool)
	if attachedOnly != nicIsAttached {
	continue
	}

This code checks if it is attached or not no matter if attached is actually set. If attached is null, it should be bypassed.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.