temporalio / temporalio/omes

[Feature Request] Support env setup step

Open
#93 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
102
Forks
29
Avg merge
1d 22h
Merged PRs (30d)
22

Description

Each scenario should be able to define the environment it expects to run in (what namespaces, search attributes, etc..) it depends on.

The exact way to express this is TBD. This functionality should work on both self-hosted servers and cloud cells.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining how scenarios are defined and executed, since the issue does not name specific files or tests. Clarify how a scenario should express namespaces and search attributes, then determine how that setup can work on both self-hosted servers and cloud cells. Done means the environment requirements are defined and supported for both deployment types.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.