microsoft / microsoft/sql-server-samples

Curious why the vnet hosting a sql jump box should not have peering relationships.

Open
#719 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
11.2k
Forks
9.1k
Avg merge
2d 7h
Merged PRs (30d)
14

Description

Hi @jovanpop-msft. Do you recall why there is a trace output printed when attachJumpbox.ps1 detects a peered network? The script continues to run even though there is a red line in the output.

https://github.com/microsoft/sql-server-samples/blob/44bd1d8d5fc41a33644cc0dfb8f7e0d06d51e5d5/samples/manage/azure-sql-db-managed-instance/attach-jumpbox/attachJumpbox.ps1#L105

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.

Research direction

Start with samples/manage/azure-sql-db-managed-instance/attach-jumpbox/attachJumpbox.ps1 at line 105 and inspect the output produced when the detected virtual network has peering relationships. Run the script with a peered network if possible, then confirm whether the red trace output is intentional and whether the final behavior should make the warning clearer or change how it is handled.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.