Documentation didn't provider explaination to configure storage_service with azure storage account

[UmanGarbag]

Hello,

I trying to configure a remote backend for my harbor instance in azure.

I have all the requirement in order to authenticate to azure.

But when i comment the parameter data_volume i get a error that someting is missing

Harbor version : 2.13.2 Docker version :

[UmanGarbag]

My configuration for storage_service are:

#data_volume: /data

storage_service:
  azure:
    accountname: "saharbor01"
      accountkey: "ACCOUNT_KEY"
    container: dataharbor
    credentials:
      type: client_secret
        clientid: "CLIENT_ID"
      tenantid: "TENANT_ID"
      secret: "SECRET"
#   # ca_bundle is the path to the custom root ca certificate, which will be injected into the truststore
#   # of registry's containers.  This is usually needed when the user hosts a internal storage with self signed certificate.
#   ca_bundle:

#   # storage backend, default is filesystem, options include filesystem, azure, gcs, s3, swift and oss
#   # for more info about this configuration please refer https://distribution.github.io/distribution/about/configuration/
#   # and https://distribution.github.io/distribution/storage-drivers/
#  filesystem:
#     maxthreads: 100
#   # set disable to true when you want to disable registry redirect
#   redirect:
#     disable: false 

When i running the script i have the following error

[MinerYang]

Hi @UmanGarbag ,

Do not comment the #data_volume: /data out. Even if you are using other storage service instead of filesystem, harbor has other persistent data to be written to the data_volume.

[reasonerjt]

Looks like a usage error.

[UmanGarbag]

Hi @MinerYang

Thanks you for the answer, can you provide some verification about the configuration i paste if needed ? I don't really know or see if is it correct or not.

so what data or put in the storage account ? Is it possible to view in debug logs the access to the storage account ?

[github-actions[bot]]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[UmanGarbag]

@reasonerjt do you have some config example working with azure sa ?