Set Temporal Namespace

[aakarim]

Tell us about the problem you're trying to solve

I have an existing Temporal cluster that I use by setting TEMPORAL_HOST in the Airbyte Kustomize definitions. I can use my existing Temporal cluster, but I can't seem to set the namespace, it always runs in the default namespace. This conflicts with my other projects and makes it difficult to see what Airbyte is up to.

I can imagine this is also relevant for users of Temporal Cloud, although I'm not one of them.

Describe the solution you’d like

An environment variable for all components that access Temporal to set a namespace.

Describe the alternative you’ve considered or used

I've looked at the source and it seems like the namespace is hardcoded, so overriding would require a fork.

Additional context

None.

Are you willing to submit a PR?

I wouldn't know where to start!

[c-p-b]

We no longer support Kustomize. Please let us know if this is an issue still in Helm

[kenske]

This still applies to Helm. I don't see an option to specify the temporal namespace in Helm.

[octavia-squidington-iii]

At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.

[kenske]

This is still an issue. It's important to have this feature so that we don't have to duplicate infrastructure for temporal.

[sepsi77]

Yes, this is important. I would prefer not to have two Temporal clusters running.

[talha-naeem1]

Facing the same problem, we should expose some environment variable to choose different temporal namespace.