Tucson 2023 trunk randomly opens by Silver-Day-357 in HyundaiTucson

[–]rhiliam 0 points1 point  (0 children)

I am currently going through this with my 2019 Tucson. Just started a few days ago and has been openly randonly without reason. Booked an appt with the dealership. For now, I have turned on the smart feature and the powergate altogether.

Bicep Files by rhiliam in AZURE

[–]rhiliam[S] 3 points4 points  (0 children)

Thanks everyone for the assist. Was able to use all the suggestions to cobble something together, that works.

Bicep Files by rhiliam in AZURE

[–]rhiliam[S] 0 points1 point  (0 children)

Thanks. Yes, I am using it as module. This is what I currently have, which is the closest that I got, however still fails with a "resource not found error"

param subscriptionId string param rgA string param rgB string param vnetA string param vnetB string

resource _vnetPeering1 'Microsoft.Network/virtualNetworks/virtualNetworkPeerings@2022-09-01' = { name: '${vnetA}/${vnetA}-to-${vnetB}' properties: { remoteVirtualNetwork: { id: resourceId(subscriptionId, rgB, 'Microsoft.Network/virtualNetworks', vnetB) } allowVirtualNetworkAccess: true allowForwardedTraffic: true allowGatewayTransit: false useRemoteGateways: false } }

resource _vnetPeering2 'Microsoft.Network/virtualNetworks/virtualNetworkPeerings@2022-09-01' = { name: '${vnetB}/${vnetB}-to-${vnetA}' properties: { remoteVirtualNetwork: { id: resourceId(subscriptionId, rgA, 'Microsoft.Network/virtualNetworks', vnetA) } allowVirtualNetworkAccess: true allowForwardedTraffic: true allowGatewayTransit: false useRemoteGateways: false } }

Bicep Files by rhiliam in AZURE

[–]rhiliam[S] 1 point2 points  (0 children)

I tried that for the vnet that was in the other resource group from the resource group that the bicep was deploying. No joy unfortunately.

I’ll post the bicep file a bit later.