Skip to content

Remove legacy configuration option#224

Merged
liam-lowe merged 2 commits into
mainfrom
liam/deprecate-legacy-config
May 5, 2026
Merged

Remove legacy configuration option#224
liam-lowe merged 2 commits into
mainfrom
liam/deprecate-legacy-config

Conversation

@liam-lowe
Copy link
Copy Markdown
Contributor

This PR removes support for legacy configuration format.

This PR:

  • migrates all repo config to new format using the config converter tool
  • removes all legacy configuration
  • removes the config converter tool
  • updates all examples / e2e / tests to use the new format

Why

  • Simplify configuration surface area to make testing easier
  • Ensure we are using the correct format across all our infrastructure
  • Ensure cluster connections config is source of truth

Breaking change

  • We have no active migrations using the legacy format.

@liam-lowe liam-lowe requested a review from a team as a code owner May 5, 2026 21:27
Comment thread config/config.go
}

// ServerTLSConfig provides backwards compatibility with existing configurations. Prefer config.ClusterConnConfig instead.
// TODO: This will be removed soon!
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When is soon? Is there a better time than now?

Comment thread proxy/proxy.go
Comment on lines +33 to +34
localHealthCheckServer *http.Server
remoteHealthCheckServer *http.Server
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to align with config. Also updated semantics above in health_check.go

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was sure what the healthCheckServer are for here.
Originally, there is just one healthCheckServer on the proxy, used by NLB.

But here, I think we want to do more. If looks closely, localHealthCheckConfig/remoteHealthCheckConfig are ConnectionConcept but somehow, it is used at proxy level (per host)

it also mentioned that localClusterHealthCheck is not implemented.

https://github.com/temporalio/s2s-proxy/blob/main/charts/s2s-proxy/files/default.yaml#L75

Let's talk to Nick about what the idea behind these healthCheckServers and leave the names as it for now.

Comment thread config/config.go Outdated
// TODO: Soon to be deprecated! Create an item in ClusterConnections instead
MemberlistConfig *MemberlistConfig `yaml:"memberlist"`
NamespaceNameTranslation NameTranslationConfig `yaml:"namespaceNameTranslation"`
SearchAttributeTranslation SATranslationConfig `yaml:"searchAttributeTranslation"`
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think SearchAttributeTranslation can be removed too.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks! fixed

Comment thread proxy/proxy.go
Comment on lines +33 to +34
localHealthCheckServer *http.Server
remoteHealthCheckServer *http.Server
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was sure what the healthCheckServer are for here.
Originally, there is just one healthCheckServer on the proxy, used by NLB.

But here, I think we want to do more. If looks closely, localHealthCheckConfig/remoteHealthCheckConfig are ConnectionConcept but somehow, it is used at proxy level (per host)

it also mentioned that localClusterHealthCheck is not implemented.

https://github.com/temporalio/s2s-proxy/blob/main/charts/s2s-proxy/files/default.yaml#L75

Let's talk to Nick about what the idea behind these healthCheckServers and leave the names as it for now.

@liam-lowe liam-lowe merged commit 3854fa7 into main May 5, 2026
5 checks passed
@liam-lowe liam-lowe deleted the liam/deprecate-legacy-config branch May 5, 2026 23:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants