Artem

@luisdavim i was not able to find this feature in kustomize docs. I found this issue, where envar proposal was rejected https://github.com/kubernetes-sigs/kustomize/issues/388#issuecomment-426457725

yes, it totally makes sense to add CLI option to set default value. Just make sure that default value remain the same.

You are correct. Unfortunately, it is not possible to do this with Chorus today. I think the ability to set a custom name for the destination bucket in the replication...

Thanks for update, we gave this feature a second thought and we think that it is makes sense to invest time in refactoring and allow sync to custom bucket name...

here is relevant feature-branch but it is far from being complete. https://github.com/clyso/chorus/compare/main...same-backend-replication i think that we will have something working in August. And we will have to develop some migration...

Hi, we implemented custom destination bucket name in [v0.5.13 release](https://github.com/clyso/chorus/releases/tag/v0.5.13). Please use new API method `POST /v2/replication/add` or `grpc AddBucketReplication` to create such replication. If custom destination is set then...

@hydro-b no, webUI is still in our internal repo. I cannot tell when it will be released and under which licence.

hi, @zap51 thank you for your interest in the project. The documentation part of the project is a little bit raw and i am happy that we can improve it....

Hi @beddari, thank you for your interest in our project. I will be happy to assist you and improve our documentation along the way! The easiest setup for a **try-out**...

one more thing that may be useful: if you are familiar with Go, you can run Chorus e2e tests against your s3 storages with debug, breakpoints, and stuff from your...