Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added the possibility for VNET to be in another subscription #463

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

AHuusom
Copy link
Contributor

@AHuusom AHuusom commented Jan 10, 2025

Summary

Added functionality to enable the use of VNets from a different subscription. This allows VMs to connect to VNets in an external subscription, addressing specific cross-subscription networking needs.

Context

While creating build server images, sysprep would fail in a subscription under Azure Defender for Cloud due to the automatic installation of agents. To resolve this issue, we moved the image creation process to a subscription without Azure Defender for Cloud.

However, due to strict network management policies, we needed to continue using an existing VNet in the original subscription.

Changes Made

  • Enabled support for associating VNets across subscriptions.
  • Ensured compatibility with existing workflows while adhering to strict network policies.

Impact

  1. Build server images can now be created in a subscription outside Azure Defender for Cloud without sysprep issues.
  2. Existing VNets in the original subscription remain in use, maintaining compliance with network management requirements.

@AHuusom AHuusom requested a review from a team as a code owner January 10, 2025 15:17
@AHuusom
Copy link
Contributor Author

AHuusom commented Jan 17, 2025

when will this be reviewed?

Copy link
Contributor

@JenGoldstrich JenGoldstrich left a comment

Choose a reason for hiding this comment

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

I am working on testing this still, but just to not make you wait longer, I wanted to give these two small pieces of feedback to start with, can you remove the 2 unrelated changes?

@@ -0,0 +1,1268 @@
ÔÇó only configurations files on version: 2 are supported, yours is version: 0 , please update your configuration
Copy link
Contributor

Choose a reason for hiding this comment

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

Please remove this file from the diff

@@ -3,6 +3,7 @@

# This is an example goreleaser.yaml file with some defaults.
# Make sure to check the documentation at http://goreleaser.com
version: 2
Copy link
Contributor

Choose a reason for hiding this comment

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

Why did you include the version bump here? I assume that the License addition also is required by goreleaser v2? Either way we generally don't expect contributors to modify our goreleaser process, can you exclude this change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants