Introduce minimal AutoFlow support with Temporal Cloud

What does this MR do?

This change set introduces minimal support for AutoFlow specifically with Temporal Cloud. It does not support anything else at this time.

This change set is required for the GitLab internal-use only deployment of the first AutoFlow experiment deployment. See gitlab-org&16181 for context. It's the most boring solution to deploy AutoFlow.

This is not meant to be enabled by our customers and is disabled by default in the chart.

Nonetheless, this change set includes minimal documentation in order for GitLab to know how to configure AutoFlow.

What is AutoFlow and Temporal?

AutoFlow is GitLab-specific, see:

AutoFlow vs. Temporal:

AutoFlow uses Temporal as a durable workflow execution server. Temporal Cloud is the SaaS version of Temporal.

Temporal is used in the internal-use experiment and considered an implementation detail. It may or may not change in the future.

Related issues

Related to

Closes Implement basic AutoFlow support in Charts (gitlab-org/gitlab#519251 - closed)

Author checklist

For general guidance, please follow our Contributing guide.

Required

For anything in this list which will not be completed, please provide a reason in the MR discussion.

  • Merge Request Title and Description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • MR has a green pipeline.
  • Documentation created/updated.
  • Tests added/updated, and test plan for scenarios not covered by automated tests.
  • Equivalent MR/issue for omnibus-gitlab opened.

Reviewers checklist

Edited by Clemens Beck

Merge request reports

Loading