You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Any Terraform configuration that defines an Azure Storage Account must declare a queue_properties block, else the pattern storage-queue-services-logging will be matched. The storage analytics log within queue_properties are only relevant for storage queues, one fourth of the functionality offered by Azure Storage Accounts.
To Reproduce
Create a terraform config declaring a storage account without a queue_properties block. E.g:
Expected behavior
This warning is not triggered from Terraform configuration that does not use a storage queue
Priority
How important is this to you?
P0: blocking me from making progress
P1: this will block me in the near future
P2: annoying but not blocking me
Additional Context
This rule is providing more noise than value, and will likely be disabled in my environment. Removing the following pattern-inside block will resolve the issue in my expected behavior scenario (tested using semgrep playground), however I recognise that this warning probably should be shown in the event of using an azurerm_storage_queue resource. As the queue_properties is defined on the Storage Account, I am not sure on the appropriate way forward.
Describe the bug
Any Terraform configuration that defines an Azure Storage Account must declare a
queue_properties
block, else the patternstorage-queue-services-logging
will be matched. The storage analytics log withinqueue_properties
are only relevant for storage queues, one fourth of the functionality offered by Azure Storage Accounts.To Reproduce
Create a terraform config declaring a storage account without a
queue_properties
block. E.g:Expected behavior
This warning is not triggered from Terraform configuration that does not use a storage queue
Priority
How important is this to you?
Additional Context
This rule is providing more noise than value, and will likely be disabled in my environment. Removing the following
pattern-inside
block will resolve the issue in my expected behavior scenario (tested using semgrep playground), however I recognise that this warning probably should be shown in the event of using anazurerm_storage_queue
resource. As thequeue_properties
is defined on the Storage Account, I am not sure on the appropriate way forward.The text was updated successfully, but these errors were encountered: