Sam Lin

> Actually I just read [goharbor/harbor-helm#1830](https://github.com/goharbor/harbor-helm/issues/1830) . Interestingly after removing the `registry.credentials` from my helm values, I am now able to login. I can confirm this. I don't even use...

I am not sure. It did pass the simple test here. https://github.com/maxisam/mgob/blob/86810b8b6dbbc6ae684ca44592a2f23ecc1c1f45/.github/workflows/build.yml#L167-L190

It is a good idea. Currently I have my own script to do the recovery thing from S3, but it will be nice to have this feature for sure. Welcome...

Please test this maxisam/mgob:dev.348 https://hub.docker.com/layers/maxisam/mgob/dev.348/images/sha256-3a584e7f9683096acfc032dfd747b6ea26d65a67a4cfc0e6c1b77938e5ae4418 https://github.com/maxisam/mgob/actions/runs/18027598142/job/51297737889

@reamasesa any chance to test it?

please test maxisam/mgob:dev.339 thx! https://hub.docker.com/repository/docker/maxisam/mgob/tags/dev.339/sha256:56b23a9a83fdfac59c4c95e7c8e9f636c633dc7353fac4d60a4faa3f1a15f69d

@erlestor any chance to test it?

I am very busy in Nov because of the black friday. But I will try to check it when i have time. Also maybe you can share how you use...

more like how do you setup that? any ref you can find for me to try?

probably should use `!Object.prototype.hasOwnProperty.call(cur.contents, path[j])`