Sergei Zaychenko
Sergei Zaychenko
TODO: revise these requirements as we are moving out some of the logic into Flows domain
The store reflects tokens of local workspace users in relation to remote API server. If the following step was done from a workspace with single-tenant repository: > Run kamu login...
@sergiimk Ready for acceptance
Alternative tooling: https://github.com/xd009642/tarpaulin
@sergiimk We always use `kamu` user in single-tenant workspaces. The local user name is only used in multi-tentant workspaces.
@demusdev Consult with @rmn-boiko for detailed supervision
As experiments in flow systems internal event bridge have shown, the following solution is the most lightweight and elegant: > 3. Relying on transaction IDs / commit timestamps, like described...
Note: failed to introduce automock for `FlowQueryService`. It seems the library is not handling non-trivial lifetimes properly.
@sergiimk I think flows should not be available in this mode. For consistency, we've implemented https://github.com/kamu-data/kamu-web-ui/issues/485, which disables `Update` button and `Flows` tabl whenever `enableScheduling` flag is not set.