Dashboards are unusable again #3562
Assignees
Labels
customer/feedback
Feedback from customers
impact/regression
Something that used to work, but is now broken
kind/bug
Some behavior is incorrect or out of spec
p1
A bug severe enough to be the next item assigned to an engineer
resolution/fixed
This issue was fixed
Milestone
Comments
jirikopecky
added
kind/bug
mikhailshilkov
added
p1
|
This issue has been addressed in PR #3566 and shipped in release v2.62.0. |
danielrbradley
added a commit
that referenced
this issue
Sep 30, 2024
Add a more understandable and unified approach to modifying existing parts of the schema. Use a function to define a resource's schema–resource & types in both the schema and metadata. This is given any existing declaration which it is allowed to modify. - If newly added types conflict with an existing type in the schema, we will raise an error. - Allows modifying any of the types associated with the custom resource. - Allow modification of both the schema and the metadata in one abstration. - Allows creation of brand new resources - the existing resource will just be nil. This allows the removal of the custom resource `Types`, `Schema` and `Meta` fields along with the associated `SchemaMixins`, `SchemaTypeMixins` and `MetaMixins` functions. ## Dashboard Fix Re-implements #3123 after it was reverted in #3500 due to breaking our ability to release. Fixes #3562 Fixes pulumi/customer-support#1737 This then re-implements the portal Dashboard customisations, but rather than blindly overwriting the existing schema elements, it manipulates specific fields as required, giving opportunity for error handling if the expected types or fields don't match.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
What happened?
Release 2.48.0 allowed creation of Azure Portal dashboards by treating part metadata as untyped JSON. This was a workaround around Azure API spec issue Azure/azure-rest-api-specs#27465.
We started porting our dashboard definitions from custom ARM template deployment initiated by Pulumi to Pulumi, but before we could finish this work this workaround was removed in release 2.54.0. Now only Markdown parts can be created by Pulumi again, which not only prevents us from creating dashboards in Pulumi but also means that we cannot use refresh for drift detection as any time we do refresh & up Pulumi tries to delete the content of dashboard.
Please consider putting the workaround back.
Original issues: #3015, #3023
Example
Examples provided in original issues.
Output of
pulumi aboutAdditional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: