Implement a sticky session interface for multiple client interfaces

[carterkozak]

==COMMIT_MSG==
Implement a sticky session interface for multiple client interfaces
==COMMIT_MSG==

[changelog-app]

Generate changelog in changelog/@unreleased

What do the change types mean?

• feature: A new feature of the service.
• improvement: An incremental improvement in the functionality or operation of the service.
• fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
• break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
  and external consumers of the service's API (e.g. customer-written software or integrations).
• deprecation: Advertises the intention to remove service functionality without any change to the
  operation of the service itself.
• manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
  performing database surgery, ...) at the time of upgrade for it to succeed.
• migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?

• ❗The break and manual task changelog types will result in a major release!
• 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
• ✨ All others will result in a minor version release.

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Implement a sticky session interface for multiple client interfaces

Check the box to generate changelog(s)

• Generate changelog entry

[carterkozak]

Naming: should this interface have a 2 somewhere? Unlike the sticky channels factory, it is meant to be stored for reuse, so there's upside to having a cleaner name. I don't have a strong opinion either way.

[jkozlowski]

I think at this point it might be time to remove the previous sticky channel implementation, that was the plan all along. 2+ seems enough to prove out it's correctness? :P

[carterkozak]

I considered naming these getChannel and create(Class<T> clientInterface) since the interface name implies sticky, but figured matching the sticky factory would be a bit more obvious for readers

[jkozlowski]

I forgot how this code works, I thought it would be harder to knock out. THanks!

[svc-autorelease]

Released 3.89.0