Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Azure SQL Firewall Rules IP parameters missing

Open
#763 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no source files, entry points, or tests. Reproduce the export with an Azure SQL firewall rule, then trace the generated ARM JSON and compare it with the portal resource. Done means the exported firewall-rule resource includes the source IP parameters and the relevant tests pass.

Written by the indexing model from the issue text.

Description

bug resource-provider

We are trying to help a customer using AzOps to Backup their Azure Infrastructure ARM configuration.
The AIM is to have history of the changes in case of accidental deletion.

We found the JSON generated form the tool missing a parameter in case of Firewall Rules applied to an Azure SQL.

To reproduce:

  • Create an Azure SQL
  • Apply a Firewall rule with a source IP Address.
  • Find the Source IP address in the generated JSON.

Here the resource in the portal:
image

Here the generated JSON:

{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"metadata": {
"_generator": {
"name": "AzOps"
}
},
"parameters": {},
"variables": {},
"resources": [
{
"apiVersion": "2022-05-01-preview",
"name": "deletedbtest/ClientIPAddress_2023-3-1_15-26-4",
"type": "Microsoft.Sql/servers/firewallRules"
}
],
"outputs": {}
}

Dominant language
PowerShell
Stars
420
Forks
174
Avg merge
16d 18h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AzOps

All issues in Azure/AzOps

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.