spec/aksConfig displaying null values for imported cluster

[cpinjani]

Rancher version:

v2.7-0b2f7fa0f878c3402ddf416a5b622327949b9348-head
aks-operator:v1.1.3-rc1

Cluster Type: Downstream AKS cluster
Issue also exists for other hosted providers.

Describe the bug
spec.aksConfig displaying null values for most the parameters for imported cluster
Values are being displayed after Editing cluster from UI

Steps

• Import Downstream AKS cluster in Rancher UI and wait for it to be Active
• Click 'View YAML' for the imported cluster

Screenshots

After Edit cluster:

Found while validating rancher/rancher#42496

[richardcase]

Confirmed as a bug and the issue is with aks-operator

[cpinjani]

@kkaempf Can we please target this issue for next release ? It would simplify Back-end automation for Imported clusters.

[mjura]

@cpinjani @richardcase It is correct behavior, according to Rancher KEv2.

[mjura]

@cpinjani I have tested this once again. Everything is alright, we are using null values to check when managed cluster needs to be updated. For imported clusters we can update only settings for Node Pools.

So it is invalid