Skip to content

Allow Azure SQL initialization from non-Azure CI runners - #55189

Open
Pepo48 wants to merge 1 commit into
keycloak:mainfrom
Pepo48:issue-55184
Open

Pepo48 wants to merge 1 commit into
keycloak:mainfrom
Pepo48:issue-55184

Conversation

@Pepo48

@Pepo48 Pepo48 commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Closes #55184

The proof that connection now works from an AWS-hosted runner (us-east-1, 3.41.210.69): https://github.com/Pepo48/keycloak/actions/runs/43607842254/job/132486414550

Closes keycloak#55184

Signed-off-by: Peter Zaoral <pzaoral@redhat.com>
@Pepo48
Pepo48 requested a review from a team as a code owner November 14, 2026 15:37
Copilot AI lite review requested due to automatic review settings November 14, 2026 15:37

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues were identified in the Azure SQL initialization changes.

No open issues 🎉

What changed in this PR

Updates Azure SQL CI initialization so GitHub-hosted runners outside Azure can connect during database setup.

Changes:

  • Detect and validate the runner’s public IPv4 address.
  • Add and remove a temporary Azure SQL firewall rule for the runner.
  • Replace server-state polling with SQL connectivity retries.
File Description
.github/​scripts/​azure/​sql/​azure_create_sql.sh Adds runner IP detection, temporary firewall-rule management, SQL connectivity retries, and cleanup during Azure SQL initialization.

Review effort: Lite

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AzureDB IT fails to initialize Azure SQL from AWS-hosted GitHub runners

2 participants