Jarek Potiuk
Jarek Potiuk
BTW. ... some conflicts to solve - so you need to rebase too
Go ahead and do the honors @gopidesupavan -> That's an interesting one as first(?) serious one to merge as a committer.. Don't be shy. We can always revert it if...
nice! Highly requested feature.
> > If we already have it in the audit log could we extract it from there in the ui/api instead of adding it to dag run table?na > >...
To be perfectly honest, the audit log concept of ours should be completely reworked if we want to continue naming it "audit log" . The way how it is currently...
Basically my "security" hat is raised by the reminder of my hair every time when I see "audit log" with the thing that we have implemented here.
Definition by Gemini- "tamper-evident", "verifiable" are crucial part of the definition: An audit log is a chronological record of system activities, capturing events, actions, and changes within a system or...
> I've always been a fan of changing from Audit Log. But then calling it Events or Log was confusing to users. Happy to think about a better one Maybe...
> Looking at the problem from a pragmatic view we can merge it now and plan a rework for audit -> structured action log in the future. Or if there...
We actually already use entrypoints - the `provider.yaml` "subset" is already exposed in providers and various provider's capabilities are available this way. They are even automatically extracted from provider.yaml's and...