Policy: ListAttributes returning incorrect FQN for retrieved values

[jakedoublev]

1. Create a namespace
2. Create an attribute definition
3. Give it a value
4. Invoke policy.Attributes.ListAttributes
5. Observe example response below, where the value FQN is /value/:

{
  "attributes": [
    {
      "id": "529124f7-e724-4c36-a395-372d7fa4093e",
      "namespace": {
        "id": "d4d45047-7d6c-4667-86b5-84fdc38da3d1",
        "name": "test.net",
        "fqn": "https://test.net",
        "active": null,
        "metadata": null,
        "grants": []
      },
      "name": "hello",
      "rule": "ATTRIBUTE_RULE_TYPE_ENUM_ALL_OF",
      "values": [
        {
          "id": "",
          "attribute": null,
          "value": "",
          "grants": [],
          "fqn": "/value/",
          "active": null,
          "subject_mappings": [],
          "metadata": null
        }
      ],
      "grants": [],
      "fqn": "",
      "active": true,
      "metadata": {
        "created_at": "2024-12-04T20:19:39.560645Z",
        "updated_at": "2024-12-04T20:19:39.560645Z",
        "labels": {}
      }
    }
  ],
  "pagination": {
    "current_offset": 0,
    "next_offset": 0,
    "total": 1
  }
}

[jakedoublev]

Closing as this was caused by my own local mucking with Postgres and forgetting to apply an FQN reindex.