[Bug]: Azure storage account blob parameters specifying in array doesn't work

[mjnovice]

Is there an existing issue for this?

• I have searched the existing issues

Affected Resource(s)

No response

Resource MRs required to reproduce the bug

The below works.

apiVersion: storage.azure.upbound.io/v1beta1
kind: Account
metadata:
  annotations:
    crossplane.io/external-create-pending: "2024-07-03T23:31:23Z"
    crossplane.io/external-create-succeeded: "2024-07-03T23:31:23Z"
    crossplane.io/external-name: storaccid7254734
    crossplane.io/paused: "false"
  creationTimestamp: "2024-07-03T23:31:09Z"
  finalizers:
  - finalizer.managedresource.crossplane.io
  generation: 3
  labels:
    clusterId: ph31-stg-pong31
    type: common
  name: ph31-stg-pong31-common
  resourceVersion: "482338"
  uid: 91d102fd-b542-4bd0-a842-b64b3322e081
spec:
  deletionPolicy: Delete
  forProvider:
    accessTier: Hot
    accountKind: StorageV2
    accountReplicationType: GZRS
    accountTier: Standard
    allowNestedItemsToBePublic: true
    blobProperties:
    - containerDeleteRetentionPolicy:
      - days: 30
      corsRule:
      - allowedHeaders:
        - '*'
        allowedMethods:
        - GET
        - HEAD
        - PUT
        - POST
        - DELETE
        allowedOrigins:
        - '*'
        exposedHeaders:
        - '*'
        maxAgeInSeconds: 600
      deleteRetentionPolicy:
      - days: 30
    crossTenantReplicationEnabled: true
    enableHttpsTrafficOnly: true
    identity:
    - identityIds:
      - /subscriptions/23bbe8ac-d31e-4f60-bc44-90d382692c20/resourceGroups/ph31-stg-pong31/providers/Microsoft.ManagedIdentity/userAssignedIdentities/ph31-stg-pong31
      type: UserAssigned
    localUserEnabled: true
    location: eastus
    minTlsVersion: TLS1_2
    networkRules:
    - bypass:
      - AzureServices

The below doesn't work

The below works.

apiVersion: storage.azure.upbound.io/v1beta1
kind: Account
metadata:
annotations:
crossplane.io/external-create-pending: "2024-07-03T23:31:23Z"
crossplane.io/external-create-succeeded: "2024-07-03T23:31:23Z"
crossplane.io/external-name: storaccid7254734
crossplane.io/paused: "false"
creationTimestamp: "2024-07-03T23:31:09Z"
finalizers:

• finalizer.managedresource.crossplane.io
  generation: 3
  labels:
  clusterId: ph31-stg-pong31
  type: common
  name: ph31-stg-pong31-common
  resourceVersion: "482338"
  uid: 91d102fd-b542-4bd0-a842-b64b3322e081
  spec:
  deletionPolicy: Delete
  forProvider:
  accessTier: Hot
  accountKind: StorageV2
  accountReplicationType: GZRS
  accountTier: Standard
  allowNestedItemsToBePublic: true
  blobProperties:
  • containerDeleteRetentionPolicy:
    • days: 30
  • corsRule:
    • allowedHeaders:
      • '*'
        allowedMethods:
      • GET
      • HEAD
      • PUT
      • POST
      • DELETE
        allowedOrigins:
      • '*'
        exposedHeaders:
      • '*'
        maxAgeInSeconds: 600
        deleteRetentionPolicy:
    • days: 30
      crossTenantReplicationEnabled: true
      enableHttpsTrafficOnly: true
      identity:
  • identityIds:
    • /subscriptions/23bbe8ac-d31e-4f60-bc44-90d382692c20/resourceGroups/ph31-stg-pong31/providers/Microsoft.ManagedIdentity/userAssignedIdentities/ph31-stg-pong31
      type: UserAssigned
      localUserEnabled: true
      location: eastus
      minTlsVersion: TLS1_2
      networkRules:
  • bypass:
    • AzureServices

### Steps to Reproduce

Create the storage account MR as explained above.

### What happened?

Specifying individual configurations in different BlobParameters array values doesn't work. It all needs to be specified in one. Not sure if this is expected behaviour

### Relevant Error Output Snippet

_No response_

### Crossplane Version

v1.16.0-up.1

### Provider Version

v1.0.0

### Kubernetes Version

v1.28

### Kubernetes Distribution

vcluster

### Additional Info

_No response_