Artem

Results 112 comments of Artem

Hi, this behaviour is controlled by `storage.createReplication` [worker config](https://github.com/clyso/chorus/blob/main/service/worker/config.yaml#L34-L35) paramenter. The default values is `false`. After setting it to `true`, chorus worker will list all existing buckets for all users...

can it be related to #53 bug? There is a problem with sync if replication was removed and added again.

@janosch-strato thank you for your contribution and sorry for the delayed response. your PR is quite large and based on commit messages, it contains multiple features. so in current state...

good idea. what do you think about implementation? should it be more generic? For example, add the following options: ```shell $ helmify --chart-merge ./dependencies.yaml --values-merge ./dependencies-values.yaml $ cat ./dependencies.yaml dependencies:...

@PG2000 good suggestion, but as i can see this approach [also goes with](https://github.com/bitnami/charts/blob/2752ca5c04ed441490c48083aa4a339de699b69c/bitnami/elasticsearch/templates/data/statefulset.yaml) `extraArgs`, `extraEnvVars`, `extraEnvVarsCM`, `extraEnvVarsSecret`. Is it makes sense to add all of these? If so, which feature...

sorry, i didn't got the question. But probably you a looking some thing like this https://github.com/arttor/helmify/blob/main/examples/app/templates/deployment.yaml#L53C24-L53C30 ```yaml resources: {{- toYaml .Values.myapp.app.resources | nindent 10 }} ``` It takes object or...

sure. I would suggest to go through Add replication code path. It starts in [AddBucketReplication handler](https://github.com/clyso/chorus/blob/66addbd468a9c822efa15bf07094b37be1d47cfb/pkg/api/grpc_handlers.go#L527) and after some validation calls [AddBucketReplicationPolicy in policy service](https://github.com/clyso/chorus/blob/66addbd468a9c822efa15bf07094b37be1d47cfb/pkg/policy/service.go#L929). Policy [Test_policySvc_BucketReplicationPolicies](https://github.com/clyso/chorus/blob/66addbd468a9c822efa15bf07094b37be1d47cfb/pkg/policy/service_test.go#L187C6-L187C46) unit test should...

> @arttor The CI process is failing, can you help me explain what the issue is. Cant understand the error It looks strange. I can see in PR diff also...

it can be related common prefix in resource name. can you try to rename it from `myapp-pdb` to `my-pdb` or `pdb`