temporalio / temporalio/features
Add features test for cloud API key over data plane
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
In this repo, when a TEMPORAL_CLIENT_CLOUD_API_KEY env var (set via org level GH secret of the same name) is present and non-empty, use it and TEMPORAL_CLIENT_NAMESPACE env var (set via org level GH var of the same name) to test against us-west-2.aws.api.temporal.io:7233 (can be put in env var too if we want). Specifically, the test should just run an execute workflow and should use a client with just the API key from a user POV, no manually set namespace headers.
Per-SDK Tickets
- Go - TODO
- Java - TODO
- Core - N/A
- TypeScript - TODO
- Python - TODO
- .NET - TODO
- Ruby - TODO
- PHP - TODO
- Temporal CLI - N/A
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing features tests and the execute-workflow entry point in this repository. Add coverage for non-empty TEMPORAL_CLIENT_CLOUD_API_KEY and TEMPORAL_CLIENT_NAMESPACE against the Temporal cloud endpoint, using only the API key from the user perspective; done means the test runs the workflow successfully without manually set namespace headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100