-
Notifications
You must be signed in to change notification settings - Fork 8
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
Deployment to Private Network #28
Comments
Hey @cbrown101 thanks for opening up an enhancement! That doesn't sound unreasonable. The team will take a look and tag you back here in this Issue when a change is in that optionally allows the use of a private IP address from an existing virtual network. |
Should be able to make use of the mock spacestation on a local machine with Visual Studio Code or from an Azure VM thanks to @bigtallcampbell. We'll get the docs updated soon with an explicit walkthrough on how you can see ground station and space station directories synchronize. |
Attempted to deploy new json file, it still requires a public IP. I need to deploy this using our internal vnet addressing while not using a public IP. |
We'll make updates to the docs to make it a bit easier, but have you tried cloning the repository and opening it with Visual Studio Code's Remote Containers? The groundstation and spacestation will be provisioned locally as containers without deploying a virtual machine to Azure. +@bigtallcampbell to provide more context |
Deployment of mock spacestation script deploys two vm instances with azure public IP's. Currently using a subscription behind an expressroute. Would like to use customer owned networking in deployment.
Can the script be updated to include deployment using a custom private IP address from existing vnet?
The text was updated successfully, but these errors were encountered: