Artem

probably the bucket is too big and chorus was not able to list all objects in time. `chorctl check` is just a wrapper around [`rclone check`](https://rclone.org/commands/rclone_check/) command. I think it...

sorry i didn't get your question. but when you start replication chorus will list all objects from source. then it will try to sync each object to destination. if object...

implemented in #75

I don't fully understand the question but there is openapi spec for chorus management API: https://petstore.swagger.io/?url=https://raw.githubusercontent.com/clyso/chorus/main/proto/gen/openapi/chorus/chorus.swagger.json You can use API directly or with [chorctl CLI](https://github.com/clyso/chorus/tree/main/tools/chorctl). There are methods to create...

user credentials currently can only be set in yaml config. Replication policy (which bucket should be copied to which storage) can be configured with api.

url will be used by bucket notifications of your source s3 storage. This means that your source s3 storage should support bucket notification and this url should be reachable to...

Good idea, but this feature should be disabled by default and controlled by [feature flag](https://github.com/arttor/helmify?tab=readme-ov-file#available-options). If flag is on, helmify should check that: - Deployment is using a config map....

is it a bugfix? can you please describe bug or add a test case reproducing the issue?

thats a great idea. a couple of questions: 1. helmify accepts list of multiple yamls in stdin. So selector should be able to filter manifests. For example, select `spec.template.spec.containers[0].ports` for...

> * A third, but less "fancy" way would be: Only allow to use this feature, when using the "-f" flag. Then the resource filenames must match the mapping filename...