fix(azure-resources): Make Monitor Diagnostic Settings a relation of generic resources #7943
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Related to #7785. Syncing
azure_monitor_diagnostic_settingsis super slow as it goes through each resource and sends a request to get the diagnostic setting sequentially.While this requires adding a new top level table, I think making diagnostic settings a relation of a generic resources table is more consistent with the rest of the plugins if we want to have concurrency.
Not a breaking change as referencing
azure_monitor_diagnostic_settingsshould still work as before