This flag is not reliable, since it relies on upgrade-provider passing the pre-check, not panicking during execution and then successfully creating a GH issue. A known failure path for GitHub Actions is OOM on the runner, which exits before this can run. Because of this common failure case, we don't use this flag in any of our providers.
Instead of a flag like this, we would recommend monitoring actions from outside the VM running the action.
This flag is not reliable, since it relies on
upgrade-providerpassing the pre-check, not panicking during execution and then successfully creating a GH issue. A known failure path for GitHub Actions is OOM on the runner, which exits before this can run. Because of this common failure case, we don't use this flag in any of our providers.Instead of a flag like this, we would recommend monitoring actions from outside the VM running the action.