Roey Berman

This is low priority for us since most users can use separate schemas for their different deployments. Happy to take a contribution if this is important to you.

Closing this due to lack of interest.

> What multiple files do you mean? Only one static config file is required. Dynamic config requires a second file only if you want to change anything from defaults, but...

> > Yeah, it's less about requiring multiple files but that multiple files are supported and there's a concept of an environment that's not ideal to expose in the interface...

@dnr https://github.com/temporalio/temporal/issues/6561

Thanks for the report. While these admin APIs are deprecated and so is `tctl` there may still be an actual issue here and we'll look into it.

> I would put this on the outbound executor and use the task type tag so we can get this coverage for all outbound tasks: > > https://github.com/temporalio/temporal/blob/117847107c19575c30d894ed7571d484146427ac/service/history/outbound_queue_active_task_executor.go#L70 In addition...

Related issue: #7658

This is something that we are discussing internally but don't have clear timelines for.

Looks like the code wants `temporal_visibility_v1*`. This is by design, we should enforce this in the helm chart. There's a way to validate chart values as shown here: https://www.arthurkoziel.com/validate-helm-chart-values-with-json-schemas/.