Azure / Azure/bicep-types-az

Bastion: Deploying Bastion with Developer Sku using Bicep

Open
#1,979 1 comment 0 reactions 0 assignees View on GitHub
Network - Bastion Service Attention
Dominant language
TypeScript
Stars
108
Forks
44
Avg merge
18h 53m
Merged PRs (30d)
29

Description

### Resource Type

Microsoft.Network/bastionHosts

### Api Version

2023-04-01

### Issue Type

Missing property(s)

### Other Notes

trying to deploy bastion dev sku using bicep
```
resource bastion 'Microsoft.Network/bastionHosts@2023-04-01' = {
name: 'name'
location: location
sku: {
name: 'Developer'
}
}
```
but it keeps throwing up this error:
```
{
"code": "BastionHostVnetIdNotProvided",
"message": "Virtual Network Id is a mandatory field for Developer BastionHost SKU.",
"details": []
}
```
so i try

```
resource bastion 'Microsoft.Network/bastionHosts@2023-04-01' = {
name: '${prefix}${currentTime}'
location: location
sku: {
name: 'Developer'
}
virtualnetwork: {
id: vnet.id
}
```
but it says:
`
The property "virtualNetwork" is not allowed on objects of type "Microsoft.Network/bastionHosts". Permissible properties include "asserts", "dependsOn", "properties", "tags". If this is an inaccuracy in the documentation, please report it to the Bicep Team.bicephttps://aka.ms/bicep-type-issues
`

### Bicep Repro

_No response_

### Confirm

- [X] I have read the troubleshooting guide and looked for duplicates.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Microsoft.Network/bastionHosts resource definition for API version 2023-04-01 and compare the Developer SKU requirements with the two Bicep snippets. Verify how the virtual network ID is represented in the type definition, then validate the corrected shape against Bicep diagnostics; done means a Developer SKU declaration accepts the required VNet reference without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.