raffis

This is also related to deep copy requests.

api v3: * Copy, Delete must be async requests. * If job fails the user get notified via the notification system

This has already been fixed in 2.1.0-alpha1 (https://github.com/gyselroth/kube-icinga/blob/dev/CHANGELOG.md). Will be part of the upcoming v2.1.0.

correction: v2.1.0-alpha2

There should probably be no history entry at all. Since there will be no point to revert to. And as soon as the document has been changed once the first...

> Hey. Thanks for the PR! But please create an issue discussion about the addition so that you don't create anything unnecessarily ;) > > I do think this is...

Just used this new command to batch review and merge hundred pr's opened by renovate (not created using multi-gitter itself). Thats also a nice use case for this command.

Query mongodb each time will be too slow. Index can not be used for aggregation $sum operations. Requesting a sum over all bytes will take a long time.

For kubernetes I recommend you have a look at https://github.com/DoodleScheduling/keycloak-controller

(Can't be reproduced from android)