Azure / Azure/azure-powershell

Null returns where object listings should be

Open
#15,791 2 comments 0 reactions 0 assignees View on GitHub
act-identity-squad ARM - Core Service Attention
Dominant language
C#
Stars
4.8k
Forks
4.3k
Avg merge
2d 17h
Merged PRs (30d)
51

Description

## Description

## Steps to reproduce

```powershell
Compare Output:
$armIse = Get-AzResource -ResourceId $armLogApp.properties.integrationServiceEnvironment.id
$armIse.properties
$armIse.properties.endpointsconfiguration
```

## Environment data

Name Value
---- -----
PSVersion 7.1.4
PSEdition Core
GitCommitId 7.1.4
OS Microsoft Windows 10.0.19043
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0

ModuleType Version PreRelease Name ExportedCommands
---------- ------- ---------- ---- ----------------
Script 6.2.1 az
```

```

## Module versions

```powershell

```

## Debug output

I noticed an inconsistency in the returns for ISE

Note the lack of firewall rules represented in the return below.

$armIse = Get-AzResource -ResourceId $armLogApp.properties.integrationServiceEnvironment.id

PS C:\Users\thatUser\gitRepos\TD\SCI_INT_Prototype> $armIse.properties

provisioningState : Succeeded
state : Enabled
integrationServiceEnvironmentId : ********************************
endpointsConfiguration : @{workflow=; connector=}
networkConfiguration : @{accessEndpoint=; subnets=System.Object[]}

$armIse.properties | convertto-json
{
"provisioningState": "Succeeded",
"state": "Enabled",
"integrationServiceEnvironmentId": "********************************",
"endpointsConfiguration": {
"workflow": {
"outgoingIpAddresses": " ",
"accessEndpointIpAddresses": ""
},
"connector": {
"outgoingIpAddresses": " "
}
},
"networkConfiguration": {
"accessEndpoint": {
"type": "Internal"
},
"subnets": [
"@{name=tdbscivnet01/ise01; id=/subscriptions/********************************/resourceGroups/coreMgmt/providers/Microsoft.Network/virtualNetworks/tdbscivnet01/subnets/ise01; type=Microsoft.Network/virtualNetworks/subnets}",
"@{name=tdbscivnet01/ise02; id=/subscriptions/********************************/resourceGroups/coreMgmt/providers/Microsoft.Network/virtualNetworks/tdbscivnet01/subnets/ise02; type=Microsoft.Network/virtualNetworks/subnets}",
"@{name=tdbscivnet01/ise03; id=/subscriptions/********************************/resourceGroups/coreMgmt/providers/Microsoft.Network/virtualNetworks/tdbscivnet01/subnets/ise03; type=Microsoft.Network/virtualNetworks/subnets}",
"@{name=tdbscivnet01/ise04; id=/subscriptions/********************************/resourceGroups/coreMgmt/providers/Microsoft.Network/virtualNetworks/tdbscivnet01/subnets/ise04; type=Microsoft.Network/virtualNetworks/subnets}"
]
}
}

Now let us look a level deeper and see what the return looks like:
PS C:\Users\thatUser\gitRepos\TD\SCI_INT_Prototype> $armIse.properties.endpointsconfiguration

workflow connector
-------- ---------
@{outgoingIpAddresses=System.Object[]; accessEndpointIpAddresses=System.Object[]} @{outgoingIpAddresses=System.Object[]}

PS C:\Users\thatUser\gitRepos\TD\SCI_INT_Prototype> $armIse.properties.endpointsconfiguration | convertto-json

WARNING: Resulting JSON is truncated as serialization has exceeded the set depth of 2.
{
"workflow": {
"outgoingIpAddresses": [
"@{address=13.64.57.95}",
"@{address=10.0.3.0/24}"
],
"accessEndpointIpAddresses": [
"@{address=10.0.3.5}"
]
},
"connector": {
"outgoingIpAddresses": [
"@{address=52.160.99.237}",
"@{address=13.93.157.249}",
"@{address=10.0.4.0/24}",
"@{address=10.0.5.0/24}"
]
}
}

```

```

## Error output

```

```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported Get-AzResource command against the integration service environment and inspect the properties and nested endpointsConfiguration values shown in the issue. Compare the returned object listings with the Azure resource data, and consider the issue done when the expected firewall and endpoint objects are returned consistently rather than as null or empty values.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
api, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.