You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 27, 2023. It is now read-only.
It would be cool to see a way to specify existing VNet when creating a new ACI instance.
Why?
One of the great use-cases for that integration is creating jumpboxes in Azure with VSCode Remote Containers extension.
Recently, there's a motion in Azure on putting all resources behind a vnet to limit any possible malicious access. One of the biggest issues of that approach is in still getting access to that resources on dev environments. Docker ACI context with VNet-join and a proper implementation in VSCode Remote Container extensions will make it easy and flexible.
PS. I can try to help when the integration is open-sourced.
ma499, gitkalz, qbikez, whimxiqal, MattMacGillivray and 25 more