[Bug]: Cannot create file share in storage account

[hobbesuk]

Is there an existing issue for this?

• I have searched the existing issues

Affected Resource(s)

storage.azure.upbound.io/v1beta1 - Share

Resource MRs required to reproduce the bug

Using these manifests (some details redacted):

apiVersion: storage.azure.upbound.io/v1beta1
kind: Share
metadata:
  name: test
spec:
  forProvider:
    quota: 50
    storageAccountName: redactedstr

---
apiVersion: storage.azure.upbound.io/v1beta2
kind: Account
metadata:
  name: redactedstr
spec:
  forProvider:
    accountKind: FileStorage
    accountReplicationType: LRS
    accountTier: Premium
    enableHttpsTrafficOnly: true
    location: North Europe
    minTlsVersion: TLS1_2
    resourceGroupName: storage
  writeConnectionSecretToRef:
    name:storage-file
    namespace: test

Steps to Reproduce

Apply the above manifests

What happened?

This error is returned:

async create failed: failed to create the resource: [{0 creating File
        Share "test" (Account "Account \"redactedstr\" (IsEdgeZone false /
        ZoneName \"\" / Subdomain Type \"file\" / DomainSuffix
        \"core.windows.net\")"): creating share: executing request: unexpected
        status 400 (400 The value for one of the HTTP headers is not in the
        correct format.) with InvalidHeaderValue: The value for one of the HTTP
        headers is not in the correct format.

        RequestId:xxxx

        Time:2024-11-06T16:48:14.6649628Z  []}]

Relevant Error Output Snippet

No response

Crossplane Version

1.16.0

Provider Version

1.7.0

Kubernetes Version

1.28.9

Kubernetes Distribution

AKS

Additional Info

No response

[hobbesuk]

I found the problem, it looks like azure only supports file shares on a premium tier that are over 100Gb in size, I was setting it to 50Gb.

Would be useful if the error could have exposed this restriction somehow. Is that possible?