feat: azure resources sub types management and first customization - #86
Merged
Merged
Conversation
APagani-Mia
marked this pull request as ready for review
August 10, 2026 07:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What this PR is for?
This PR is meant to allow sub-types customization starting from the types managed by Azure provider itself.
The mechanism of the sub-types customization at the moment is hardcoded in Azure source, thus new expansions need a few changes in the source.
A possible example scenario is the one when an Azure Function App is created/modified/deleted, the event arrives under
Microsoft.Web/sitestype instead of its ownMicrosoft.Web/sites/functionsconsidering the Azure Resource Graph.With this feature is it now possible to create two items one for the parent type and another one for the specific sub-type, these two items can also be linked together with a relationship between them.
The shape of the parent and sub-type items and the relationship items are still defined with a Go Template mapping file.
This scenario of Azure Function App it actually the first implemented in the code, this same mechanism could be implemented in the future for other resources with similar needs.