Wenkai Yin(尹文开)

@laurivosandi Yes, I can confirm that. Our internal Harbor instance deploys multiple registry pods with NFS as the underlying storage system

Let's update the doc to declare that it's users' responsibility to make sure the `registry.credentials.username` and `registry.credentials.password` match `registry.credentials.htpasswdString`

What is the version of Harbor chart you are using? Is it a fresh installation or upgrade one?

@yvespp Sorry for the late review. I have added some comments but haven't reviewed the [delegationsas.go](https://github.com/vmware-tanzu/velero-plugin-for-microsoft-azure/pull/111/files#diff-1d780eb4040da13fa413bf2491ee1595a92a19977f6aeb27e66cb8a668377042) yet and I will continue to add comments.

@yvespp The object store uses the new version of Azure SDK to do the auth and operations in this PR, but the snapshotter still uses the old one. Is it...

@yvespp I have finished all the reviewing and thanks very much for the contribution. I'll trigger end-to-end testing to test the new plugin and will let you know the result

The BSL validation still doesn't work with the error: ``` RESPONSE 403: 403 This request is not authorized to perform this operation using this permission. ERROR CODE: AuthorizationPermissionMismatch ```

And I find another issue: as we change the needed permissions for the customized role, if users use the customized role, this introduces break change for them

So this is the reason that I got the `AuthorizationPermissionMismatch` error as I still use the old credential with only `Contributor` role. I'm afraid this breaking change isn't acceptable, this...

@yvespp Thanks for the quick update. I think we need a new major version(v2.x) to introduce such kinds of breaking changes, so it may be a long time before we...