-
Notifications
You must be signed in to change notification settings - Fork 826
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
virtual network manager - New Terraform Template - Quickstart Create virtual network manager with Management Group Scope #298
virtual network manager - New Terraform Template - Quickstart Create virtual network manager with Management Group Scope #298
Conversation
quickstart/101-virtual-network-manager-create-management-group-scope/readme.md
Outdated
Show resolved
Hide resolved
quickstart/101-virtual-network-manager-create-management-group-scope/providers.tf
Outdated
Show resolved
Hide resolved
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.
Thanks @mbender-ms for opening this pr! Some comments.
quickstart/101-virtual-network-manager-create-management-group-scope/main.tf
Show resolved
Hide resolved
quickstart/101-virtual-network-manager-create-management-group-scope/providers.tf
Outdated
Show resolved
Hide resolved
As I recall, those values were specified to me by someone on the terraform team during the creatin process of the original. I did
version = "~> 3.56.0, < 4.0" |
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.
Applied all review suggestions.
If you're going to explicitly state a min & max, then you don't need the pessimistic operator. Personally, I'd use "~>3.56" (without the max), which states min=3.56 and max is anything less than 4. However, the way you have it now (and had it before) both function. Therefore, for me, this is not a blocking issue. @lonegunmanb @stemaMSFT I believe that @grayzu is OOF for Thanksgiving. Could one of you merge this PR? |
Sure. Yesterday this e2e test failed because we don't have |
We've got the following error:
I'll see what we can do to fix this issue. |
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.
approved
@lonegunmanb It looks like pre-check is now failing. Any ideas? |
Hi @mbender-ms it looks like your branch is outdated, would you please rebase your branch with the latest master branch and try again? Thanks! |
#please-close |
#please-open |
@TomArcherMsft @lonegunmanb Anything I'm missing to get this rolling? My branch is updated. Looks like there is still a change request but that has been completed. Thanks! |
@mbender-ms looks like the prepr-check is failing, if you could get that resolved I can kick off tests again. |
@stemaMSFT Looks like I was missing some quotes. Fixed that so let's try again! |
@mbender-ms the e2e tests failed here, take a look with Tom if needed and resolve and we can re-kick off the tests |
Unfortunately, I know nothing about management groups. If Michael doesn't know, maybe @lonegunmanb can help. |
Hi @mbender-ms @TomArcherMsft , I want explain this testing error and my solution step by step here, so we can fix this issue and get this pr merged. The testing error
Root cause: Because we use How can we
|
@lonegunmanb Thanks for your help on this. I'm currently unable to follow your steps to pull your repo into my branch. I'm nuking my local and going to see if that fixes things. I'll keep you posted. |
32d9cca
to
99037bb
Compare
@lonegunmanb Force pushed your changes into my branch. Please let me know if this fixes it and lets PR pass. |
@mbender-ms thanks to your efforts, this PR is merged! |
No description provided.