David Tesar

This I believe we're deciding is not set until RC-2 per the linked user stories which we discussed on the last community call: https://github.com/notaryproject/notation/issues/245 https://github.com/notaryproject/notation/issues/246

This theoretically should work now by [enabling the preview API ](https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/4617) and the [CAPZ patch mechanism to enable this feature](https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/4527). @paulapetri - would you like to try this out?

Unfortunately, I don't see any diff in the `asoctl` yaml export after enabling this preview feature. So without the ASO diff, the ASO patch won't do anything of course. Using...

Thanks for the pointer! All I got was this from [the ManagedClustersAgentPool](https://azure.github.io/azure-service-operator/reference/containerservice/v1api20231102preview/#containerservice.azure.com/v1api20231102preview.ManagedClustersAgentPool): ``` --- apiVersion: containerservice.azure.com/v1api20231001 kind: ManagedClustersAgentPool metadata: creationTimestamp: null name: pool1 spec: azureName: pool1 count: 1 enableAutoScaling: false...

Thanks Matt and Bevan! I think a generic flag like `--prefer-preview-versions` would work great and no need for more granular especially since you're already specifically asking for import of a...

> In any case, I don't' think you specifically need `asoctl` to define the diff, it's just a convenient way to see what you need to add, right? Right, `code...

/remove-lifecycle stale @nawazkh would be great to test this out. Related to #4957

/ok-to-test

How would this work with CAPZ new ASO v2 API? @nojnhuh @nawazkh

related to #4699