Introduceon_failure attribute to theaction_trigger block.
This attribute will allow consumers to define the behavior if an action fails.
As of now we default to failing run if an error has been returned as part of action invocation.
We'll keep that the default behavior but introduce two options:

on_failure: failon_failure: continue

fail is the default behavior - we're just making our choice explicit.
continue is the new behavior we're adding - it will instruct terraform to ignore errors from the action invocation, log that the error has occurred and continue with the run execution.

Theon_failure attribute takes inspiration from the namesake attribute in provisioners.

Example configuration

resource "tfcoremock_simple_resource" "test_resource" {  id     = "test-resource"  string = "This is a message"  lifecycle {    action_trigger {      events = [before_create]      actions = [        action.tfcoremock_simple_resource.example      ]      on_failure = continue    }  }}action "tfcoremock_simple_resource" "example" {  config {    string = "Hello from action"  }}

Testing

In order to manually test this feature one should use a provider that allows for controlled erroring of actions. For that purpose I've used the modifiedtfcoremock[GH] provider which will always fail on the action invocation.

Fixes #

Target Release

1.15.x

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

CHANGELOG entry

Addon_failure attribute to theaction_trigger block to allow defining different behavior on action failure. For now we support the defaultfail keyword as well as the newcontinue keyword which instructs terraform to ignore action failure and continue with the run.

• This change is user-facing and I added a changelog entry.
• This change is not user-facing.