Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Arc custom locations no longer appear in CustomLocationListStep #1000

Closed
bwateratmsft opened this issue Sep 16, 2021 · 1 comment · Fixed by #1006
Closed

Azure Arc custom locations no longer appear in CustomLocationListStep #1000

bwateratmsft opened this issue Sep 16, 2021 · 1 comment · Fixed by #1006

Comments

@bwateratmsft
Copy link
Contributor

I've noticed that Azure Arc custom locations stopped appearing in CustomLocationListStep. The graph query we are making is returning no results.

@bwateratmsft
Copy link
Contributor Author

bwateratmsft commented Sep 16, 2021

As far as I can tell they changed the shape of the Resources object.

Our graph query:

Resources
| where type contains 'Microsoft.Web/kubeEnvironments'
| project kubeEnvironment=pack('id', id, 'name', name, 'location', location, 'properties', properties), customLocationId=tolower(tostring(properties.extendedLocation.customLocation))
| where isnotnull(customLocationId)
| join (Resources
    | where type contains 'Microsoft.ExtendedLocation/customLocations'
    | project name, customLocationId=tolower(tostring(id)), id) on customLocationId
| project kubeEnvironment, name, id

The current shape of the object:

    {
      "extendedLocation": {
        "name": "/subscriptions/baadf00d-baad-f00d-baad-f00dbaadf00d/resourcegroups/bwaterarc3/providers/microsoft.extendedlocation/customlocations/bwaterarc3-custom-location",
        "type": "CustomLocation"
      },
      "id": "/subscriptions/baadf00d-baad-f00d-baad-f00dbaadf00d/resourceGroups/bwaterarc3/providers/Microsoft.Web/kubeEnvironments/bwaterarc3-kubeenv",
      "identity": null,
      "kind": "",
      "location": "eastus",
      "managedBy": "",
      "name": "bwaterarc3-kubeenv",
      "plan": null,
      "properties": {
        "aksResourceID": null,
        "appLogsConfiguration": null,
        "arcConfiguration": {
          "artifactStorageAccessMode": null,
          "artifactStorageClassName": "default",
          "artifactStorageMountPath": null,
          "artifactStorageNodeName": null,
          "artifactsStorageType": "NetworkFileSystem",
          "frontEndServiceConfiguration": {
            "kind": "LoadBalancer"
          },
          "kubeConfig": null
        },
        "defaultDomain": "bwaterarc3-kubee-baadf00d.eastus.k4apps.io",
        "deploymentErrors": null,
        "extendedLocation": null,
        "internalLoadBalancerEnabled": false,
        "provisioningState": "Succeeded",
        "staticIp": "11.11.11.11",
        "type": null,
        "workerAppsConfiguration": null
      },
      "resourceGroup": "bwaterarc3",
      "sku": null,
      "subscriptionId": "baadf00d-baad-f00d-baad-f00dbaadf00d",
      "tags": {},
      "tenantId": "baadf00d-baad-f00d-baad-f00dbaadf00d",
      "type": "microsoft.web/kubeenvironments",
      "zones": null
    }

I'm noticing that properties.extendedLocation is now null, with an extendedLocation object at the root.

Maybe the query needs to be updated to:

Resources
| where type contains 'Microsoft.Web/kubeEnvironments'
| project kubeEnvironment=pack('id', id, 'name', name, 'location', location, 'properties', properties, 'extendedLocation', extendedLocation), customLocationId=tolower(tostring(extendedLocation.name))
| where isnotnull(customLocationId)
| join (Resources
    | where type contains 'Microsoft.ExtendedLocation/customLocations'
    | project name, customLocationId=tolower(tostring(id)), id) on customLocationId
| project kubeEnvironment, name, id

Though I'm not certain how the properties object is used, and if extendedLocation needs to be there for later consumption.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant