Azure / Azure/bicep-registry-modules
[AVM Module Issue]: Missing the option to add publicIPAddressObject in Bastion configuration
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 737
- Forks
- 564
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 30
Description
Check for previous/existing GitHub issues
- I have checked for previous/existing GitHub issues
Issue Type?
Bug
Module Name
avm/ptn/network/hub-networking
(Optional) Module Version
0.4.0
Description
I tried adding publicIpAdressObject to the Bastion section, but it isn't available. I had a look at the bicep file it uses 'br/public:avm/res/network/bastion-host:0.6.1' That has the option. It's very much like the AzureFirewallSettings section.
(Optional) Correlation Id
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the Bicep for avm/ptn/network/hub-networking version 0.4.0, focusing on the Bastion configuration and its comparison with the AzureFirewallSettings section. Check the referenced br/public:avm/res/network/bastion-host:0.6.1 module for publicIPAddressObject; done means that option can be configured through the hub-networking module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100