Fix deployment errors in OpenDataFunctions.kql

[Brett Wilson (MSBrett)]

🛠️ Description

This PR fixes deployment caused by

• shortening the length of the OpenDataFunctions.kql script script to less than 131K chars
• casting the type of data returned in tmp_resourcedetails to string.

🔬 How did you test this change?

• 🤏 Lint tests
• 🤞 PS -WhatIf / az validate
• 👍 Manually deployed + verified
• 💪 Unit tests
• 🙌 Integration tests

🙋‍♀️ Do any of the following that apply?

• 🚨 This is a breaking change.
• 🤏 The change is less than 20 lines of code.

📑 Did you update docs/changelog.md?

• ✅ Updated changelog (required for dev PRs)
• ➡️ Will add log in a future PR (feature branch PRs only)
• ❎ Log not needed (small/internal change)

📖 Did you update documentation?

• ✅ Public docs in docs (required for dev)
• ✅ Internal dev docs in src (required for dev)
• ➡️ Will add docs in a future PR (feature branch PRs only)
• ❎ Docs not needed (small/internal change)

[Copilot]

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

src/templates/finops-hub/modules/scripts/IngestionSetup.kql:1253

• The newly introduced ResourceName variable should be covered by tests to ensure its correct behavior.

| extend ResourceName = tostring(tmp_ResourceDetails.ResourceName)

[Roland Krummenacher (RolandKrummenacher)]

My VS code is telling me that it is still 132138 characters. I can't deploy it: Error BCP184: File 'C:\Projects\finops-toolkit\src\templates\finops-hub\modules\scripts\OpenDataFunctions.kql' exceeded maximum size of 131072 characters.

[Michael Flanakin (flanakin)]

How are you deciding what to keep and what to remove?

[Michael Flanakin (flanakin)]

I don't love removing values. While I feel there has to be a better solution, I submitted a PR to split the file into multiple files since we know it will grow over time. I don't love it, but it should get us past the current issue. I validated the deployment so it should resolve the current issues. Thanks for digging into this.

#1269

[Michael Flanakin (flanakin)]

Closing in favor of #1269