feat(queries): implemented queries to check if managed identity is not enabled #7863
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.








Closes #
Reason for Proposed Changes
identityblock is not enabled, i.e., by having a blockidentitydefined with thetypefield with the valuesSystemAssignedandUserAssignedor both(except for the resource of typeazurerm_kubernetes_clusterthat only can have one of the values at time, according to its documentation).identityblock is defined.Beta - Container Group Managed Identity Disabled:azurerm_container_groupBeta - Kubernetes Cluster Managed Identity Disabled:azurerm_kubernetes_clusterBeta - Container App Managed Identity Disabledazurerm_container_appBeta - App Service Slot Managed Identity Disabledazurerm_app_service_slotazurerm_linux_web_app_slotazurerm_windows_web_app_slotBeta - Logic App Managed Identity Disabledazurerm_logic_app_standardProposed Changes
identityis defined is enough because the fieldtypeis required and the only values that can be defined within are the ones mentioned above.I submit this contribution under the Apache-2.0 license.