-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
terraform_azure_example_test.go Type Issue #522
Comments
Definitely looks like a bug in the test! Could you use the |
Please see #89 for the status on Terratest with Azure. In particular, we're starting some work around it, and when that work is done, we'll be able to come back to this question! |
Hi @neal-shah, Are you still having the problem with the assert failing? There have been several updates to the Azure compute module since then and I would like to help if needed. |
Hey @davesee, Apologies it's been a while since I looked at this! I'll try and find some time hopefully in the next week or so, and let you know! I've been working on AWS and GCP recently so have left Azure on the back-burner. Cheers! |
Hi @davesee, I just run into above problem with the virtual machine example test. Names are the same but comparison fails. Error: Not equal: Both errors come from the compute library from azure-sdk-for-go. Can this be the reason? |
Hey @mjooz The sdk package version should not matter since both module and test use the same version. You can update them and try of course. I ran both _example and _vm_example and was not able to reproduce the error. I added this to see the types, perhaps see if you get something other than string. Also you can try the assert.EqualValues to be less strict.
results
Hope this helps! |
Hi @davesee, issue was (and still is) with Go version and stretchr/testify package - errors from above are present if Go 1.16.2 is used. |
I am running the example test in terraform_azure_example_test.go, however I'm getting the following test failure:
Go: 1.14.2 darwin/amd64
Terraform: v0.12.24
Any idea's?
The text was updated successfully, but these errors were encountered: