add gitaudit autoflush #202

Merged

cmo merged 1 commit from gitaudit_auto_flush into master

2026-03-23 08:06:25 +00:00

cmo commented

2026-03-22 20:25:50 +00:00

Owner

This commit adds the configuration auto_flush_timeout to
the gitaudit-configuration. If auto_flush_timeout seconds
have passed without adding a new audit log entry and there
is a non-empty changeset, i.e., the changeset was last
touched more than auto_flush_timeout seconds ago, the
changeset will be persisted. This results in a commit.

For example, if auto_flush_timeout is 60, but every 50
seconds a log-entry for a new record is added to the
gitaudit-instance, the automated persisting of the
changeset will never be triggered (the changeset might
still be persisted, depending on the content of the
changes).

If, on the other hand, a single change was added and
no other change is added in the next auto_flush_timeout
seconds, the single change will be persisted,
resulting in a commit with a single change.

This commit adds the configuration `auto_flush_timeout` to the gitaudit-configuration. If `auto_flush_timeout` seconds have passed without adding a new audit log entry and there is a non-empty changeset, i.e., the changeset was last touched more than `auto_flush_timeout` seconds ago, the changeset will be persisted. This results in a commit. For example, if `auto_flush_timeout` is 60, but every 50 seconds a log-entry for a new record is added to the gitaudit-instance, the automated persisting of the changeset will never be triggered (the changeset might still be persisted, depending on the content of the changes). If, on the other hand, a single change was added and no other change is added in the next `auto_flush_timeout` seconds, the single change will be persisted, resulting in a commit with a single change.

cmo added 1 commit

2026-03-22 20:25:50 +00:00

add gitaudit autoflush

Test execution / Test-all (push) Successful in 1m56s

Details

ac3a3c9533

This commit adds the configuration `auto_flush_time` to
the gitaudit-configuration. If `auto_flush_time` seconds
have passwd without adding a new audit log entry and there
is a non-empty changeset, i.e., the changeset was last
touched more than `auto_flush_time` seconds ago, the
changeset will be persisted. This results in a commit.

For example, if `auto_flush_time` is 60, but every 50
seconds a log-entry for a new record is add to the
gitaudit-instance, the automated persisting of the
changeset will never be triggered.

If, on the other hand, a single change was added and
no other change is added in the new `auto_flush_time`
seconds, the single change will be persisted,
resulting in a commit with a single change.

cmo force-pushed gitaudit_auto_flush from ac3a3c9533

Test execution / Test-all (push) Successful in 1m56s

Details

to f20daac102

Test execution / Test-all (push) Successful in 1m52s

Details

2026-03-23 08:00:53 +00:00

Compare