`io.quarkus.oidc.client.*` packages are split across multiple modules

[dmlloyd]

The packages are split as follows:

• io.quarkus.oidc.client.filter in:
  • extensions/oidc-client/runtime
  • extensions/oidc-client-filter/runtime
• io.quarkus.oidc.token.propagation in:
  • extensions/oidc-client/runtime
  • extensions/oidc-token-propagation/runtime

[quarkus-bot]

/cc @pedroigor (oidc), @sberyozkin (oidc)

[michalvavrik]

This one needs an agreement what to do @sberyozkin . You moved @AccessToken under OIDC client for a good reason #29147, but now, we need to use io.quarkus.oidc.token.propagation package in both OIDC client and OIDC Token Propagation extensions. I think we need to:

• create a new @AccessToken in io.quarkus.oidc.token.propagation
• deprecate @AccessToken in io.quarkus.oidc.token package
• provide recipe that update this for users
• wait for 2 LTS and then drop the @AccessToken in io.quarkus.oidc.token

Agreed?

[michalvavrik]

proposing to make the first step here #45923

[gsmet]

wait for 2 LTS and then drop the @accesstoken in io.quarkus.oidc.token

As long as the deprecation is in one LTS, it's fine and can be removed in a release after LTS.

[michalvavrik]

wait for 2 LTS and then drop the @accesstoken in io.quarkus.oidc.token

As long as the deprecation is in one LTS, it's fine and can be removed in a release after LTS.

Cool! I think I heard the 2 LTS thing somewhere, but I can't remember where, it could be product of my fantasy as well.

[gsmet]

What we need to make sure of is that we have proper warnings and documentation for deprecation in one LTS so that people can act on it if they only update from LTS to LTS.