Closed annaFaralliCR closed 1 month ago
Hi @annaFaralliCR thank you for reporting this.
Unfortunately, the only DashboardPartMetadata
I see in the Open API spec is MarkdownPartMetadata
: https://github.com/Azure/azure-rest-api-specs/blob/85441dcd442a3c58f5bdf867b94d3bbb147e506b/specification/portal/resource-manager/Microsoft.Portal/preview/2020-09-01-preview/portal.json#L477
Unless I miss something here, would you be so kind to open a request in the Open API issues for this?
I stumbled across the same issue. I am migrating to azure-native provider, but these Azure dashboards are a blocker for us.
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/azure-portal/azure-portal-dashboards-create-programmatically.md proves that there are way more tile types than markdown tiles. With the classic azure provider, I created GO structs --> marshalled them into a json string and done... Now we have to use Pulumi Go types which is a nightmare for such complex resources. https://www.pulumi.com/arm2pulumi/ is also failing because it cant understand the models, Azure uses.
This issue has been addressed in PR #3566 and shipped in release v2.62.0.
Description:
Currently, Pulumi only accepts Extension/HubsExtension/PartType/MarkdownPart value for lenses.part.metadata.type in module @pulumi/azure-native/portal/dashboard.
However, more values should be available, e.g. Extension/HubsExtension/PartType/MonitorChartPart.
An example of this could be:
which returns the error: The type of dashboard part. Expected value is 'Extension/HubsExtension/PartType/MarkdownPart'.