-
Notifications
You must be signed in to change notification settings - Fork 381
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
adding azure gaming: gdvmss #120
Conversation
Closes #121 |
@bmoore-msft , in order to run the tests I need to have the VM Offer approved. publisher='microsoft-azure-gaming' offer = 'game-dev-vm', sku = 'win10_unreal_4_27_2' |
@dciborow Give me some time to accept the legal terms of the image on the subscription, which should fix the test failure. |
@dciborow Do you mind taking a look at #121 (comment)? |
@shenglol , this is ready for review |
@dciborow Posting the question that Alex asked in the module proposal here in case you missed it: |
@alex-frankel Are we good with the changes? If yes, I can start the MCR manifest onboarding process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have a small change, but it is not blocking and can happen later.
Can we take an action item to further debug why the vnet module was not working? Maybe myself, @dciborow, @MrMCake can all sit down together and see if we can figure it out? I'd really like to move back to the vnet module in the registry at some point.
Co-authored-by: Shenglong Li <[email protected]>
@alex-frankel , we fixed it. this now uses the module, (but still within my own virtualNetwork.bicep) |
febb003
to
a760617
Compare
Thanks! @shenglol this is ready to merge from my perspective |
Description
Closes #121
If you haven't already, read the full contribution guide. The guide may have changed since the last time you read it, so please double-check. Once you are done and ready to submit your PR, edit the PR description and run through the relevant checklist below.
Adding a new module
brm validate
locally to verify the module files.Updating an existing module
brm validate
locally to verify the module files.version.json
file properly:version.json
.version.json
.version.json
.