fix(observability-lib): use int64 for Folder.ID to match Grafana API

[leeyikjiun]

Summary

Fix JSON unmarshaling error when deploying Grafana dashboards due to Folder.ID type mismatch.

Problem

Grafana's API returns -1 for folder IDs in certain cases (e.g., with nested folders feature enabled in Grafana 11.6+). The previous uint type cannot represent negative values, causing deployment to fail with:

Error: failed to deploy dashboard: could not find or create folder: error making API request: json: cannot unmarshal number -1 into Go struct field Folder.id of type uint

Solution

Changed Folder.ID from uint to int64 to match Grafana's official Go client:
https://github.com/grafana/grafana-api-golang-client/blob/master/folder.go

type Folder struct {
    ID    int64  `json:"id"`
    UID   string `json:"uid"`
    Title string `json:"title"`
    URL   string `json:"url"`
}

Testing

• Verified dashboard deployment succeeds after the fix
• The change is backwards compatible (positive IDs work the same)

[Copilot]

Pull request overview

This PR fixes a JSON unmarshaling error during Grafana dashboard deployment by changing the Folder.ID field type from uint to int64 to handle negative folder IDs returned by Grafana's API.

Changes:

• Updated Folder.ID type from uint to int64 to align with Grafana's official Go client
• Added inline comment explaining the rationale for using int64

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

✅ API Diff Results - No breaking changes

---

📄 View full apidiff report