Allow for Customization of Polaris Authorizer

[travis-bowen]

Want to be able to allow for Polaris Authorizer to be customizable at the request level, while still maintaining existing behavior of a single application level implementation.

[dimas-b]

Thanks for your interest and contribution, @travis-bowen !

Your code changes make sense to me, however, if your intention is to have an alternative PolarisAuthorizer in a downstream build (not in this repo), I believe these changes are not necessary. The downstream build could have an overriding producer method like this:

  @Produces
  @Alternative
  @Priority(10)
  @Singleton
  public PolarisAuthorizer polarisAuthorizer(...) {...}

to cause a different implementation to be used. You can have any config and other beans injected into the producer method depending on its needs. WDYT?

[travis-bowen]

If this is contentious I can probably change back to ApplicationScoped and utilize the call context within my own implementation to do different things per request.

[travis-bowen]

Thanks for the input @dimas-b ! I'm pretty new to the Quarkus stuff so let me try that out!