Skip to content

azurerm_security_center_storage_defender - add malware_scanning_on_upload_filters and malware_scanning_write_results_on_tags_enabled properties #18207

azurerm_security_center_storage_defender - add malware_scanning_on_upload_filters and malware_scanning_write_results_on_tags_enabled properties

azurerm_security_center_storage_defender - add malware_scanning_on_upload_filters and malware_scanning_write_results_on_tags_enabled properties #18207

Triggered via pull request March 27, 2026 03:14
@v-yhyeo0202v-yhyeo0202
synchronize #31964
Status Success
Total duration 10s
Artifacts

pull-request-new-commit.yaml

on: pull_request_target
remove-waiting-response  /  remove-label
4s
remove-waiting-response / remove-label
Fit to window
Zoom out
Zoom in

Annotations

1 warning
remove-waiting-response / remove-label
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/