Skip to content

v3 Provider appears to randomly remove helm_release resources from TF state - Hard to reproduce #1871

v3 Provider appears to randomly remove helm_release resources from TF state - Hard to reproduce

v3 Provider appears to randomly remove helm_release resources from TF state - Hard to reproduce #1871

Triggered via issue March 12, 2026 21:06
Status Failure
Total duration 27s
Artifacts

jira-issues.yml

on: issue_comment
Jira Community Issue sync
22s
Jira Community Issue sync
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Jira Community Issue sync
Process completed with exit code 1.
Jira Community Issue sync
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: atlassian/gajira-login@ca13f8850ea309cf44a6e4e0c49d9aa48ac3ca4c. 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/