Hi Pat,
Remote signing sounds a good idea! Looking forward to a proposal/design doc.
Yufei
On Fri, Aug 1, 2025 at 8:44 AM Pat Patterson
wrote:
> Hi,
>
> I'm Pat Patterson, Chief Technical Evangelist at Backblaze. I've
> been working with Backblaze B2, our S3-compatible cloud object store, and
Thanks for chiming in, JB. You're right, the discussion around Generic
Tables isn't necessarily tied to a specific release. That said, aligning
its GA with a release still makes sense, as reflected in the roadmap.
I've created the 1.1.0-blocker label. Feel free to apply it to any relevant
issues o
> In practice though it is possible that different realms get bootstrapped
with different database schemas and I think we should try to make the
service resilient to situations like this
+1 on this. Each realm could have its own schema, or even different
Postgres server. A bit more context on it,
> If the same endpoint works for both the engine and the Polaris Server, it
is only necessary to set one "endpoint" parameter.
That's right, we will only need one endpoint in that case. However, if
there is no one endpoint can work for both engines and Polaris server, the
extra new endpoint makes
Hi all,
ActiveRolesProvider was introduced back in January, in order to enrich
SecurityContext with valid roles for a given principal.
But that was before the introduction of Quarkus, and the introduction
of external authentication with Quarkus Security and OIDC.
TLDR: ActiveRolesProvider became
RIght, the idea is to have a "common abstraction" first.
I'm actively looking into exactly that at the moment. WIll come up
with a couple PRs to enable this.
Some of it is implicitly covered by the work that Christopher's
contributing, although it's rather orthogonal.
On Fri, Aug 1, 2025 at 6:54 P
