Skip to content

policy_definition_resource: Force recreation when policy definition parameter names change #10585

policy_definition_resource: Force recreation when policy definition parameter names change

policy_definition_resource: Force recreation when policy definition parameter names change #10585

Triggered via pull request March 18, 2026 05:19
Status Success
Total duration 7m 28s
Artifacts

static-analysis.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 warning
detect
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/