Issue 206: Conditional execution in saga

[krasimirr]

Description

Currently, there are cases when tasks/workflows need to be executed only if a condition is matched based on a saga state value. This feature implements that requirement.

Checklist

• Lint and unit tests pass locally with my changes
• I have added relevant error handling and logging messages to help troubleshooting
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• I have updated CHANGELOG.md with a short summary of the changes introduced
• I have tested against live environment, if applicable
• I have added relevant usage information (As-built)
• Any structure and/or content vRA-NG improvements are synchronized with vra-ng and ts-vra-ng archetypes
• Every new or updated Installer property is documented in docs/archive/doc/markdown/use-bundle-installer.md
• Dependencies in pom.xml are up-to-date
• My changes have been rebased and squashed to the minimal number of relevant commits
• My changes have a descriptive commit message with a short title, including a Fixed #XXX - or Closed #XXX - prefix to auto-close the issue

Testing

YAML:

Workflow:

Action:

Release Notes

This feature enables the conditional execution of tasks/workflows based on a conditional variable (saga state value).

tasks:
  TestOne:
    execute: testSagaTask
    if: conditionalVariable # Newly introduced variable
  TestTwo:
    workflow: workflowId
    if: conditionalVariable # Newly introduced variable

Related issues and PRs

[vmwclabot]

@krasimirr, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit afc0864 must be signed by rkrasimir@vmware.com

[vmwclabot]

@krasimirr, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit afc0864 must be signed by rkrasimir@vmware.com

[vmwclabot]

@krasimirr, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit afc0864 must be signed by rkrasimir@vmware.com

[vmwclabot]

@krasimirr, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit afc0864 must be signed by rkrasimir@vmware.com

[Michaelpalacce]

Nice job :) a few comments only

[Michaelpalacce]

Would be good to add test for workflows as well, ideally separately, so we can figure out where the error is if it happens faster

[Michaelpalacce]

Lgtm