Should remove the "host/" prefix of blob name when the blob container is set to "IsMultiTenant = false"?

[gdlcf88]

abp/framework/src/Volo.Abp.BlobStoring.Azure/Volo/Abp/BlobStoring/Azure/DefaultAzureBlobNameCalculator.cs

Lines 15 to 20 in 87cb329

	public virtual string Calculate(BlobProviderArgs args)
	{
	return CurrentTenant.Id == null
	? $"host/{args.BlobName}"
	: $"tenants/{CurrentTenant.Id.Value.ToString("D")}/{args.BlobName}";
	}

abp/framework/src/Volo.Abp.BlobStoring/Volo/Abp/BlobStoring/BlobContainer.cs

Lines 206 to 214 in cdae51b

	protected virtual Guid? GetTenantIdOrNull()
	{
	if (!Configuration.IsMultiTenant)
	{
	return null;
	}
	return CurrentTenant.Id;
	}

If a blob name is something, and the blob container is set to IsMultiTenant = false, the actual blob name will be host/something, but I think the blob name should be something itself.

[hikalkan]

What if you later change your application to be multi-tenant? All your BLOB data become lost. I suppose I did it intentionally because of this reason.

[gdlcf88]

Hi @hikalkan,

I think when it is changed to be multi-tenant, developers should handle the existing BLOBs themself.

But, maybe the above need should not exist. A BLOB container with IsMultiTenant = false is usually used to store system-level BLOBs (such as certificates). If there is a container that may need multi-tenancy, it should be set IsMultiTenant = true even if there is only one tenant (host) currently.

In the current design, if a BLOB container is changed to be multi-tenant, BLOBs of any tenant are still stored in "host/", it is not expected (either before or after the change). And the essential reason is that the "non-multi-tenant" may be different from "arrange all tenants as the host".

[hikalkan]

#5510 (comment)