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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
@nitrocode recommended in #4462 (comment) that we pin terraform versions in tests. I didn't want to block that particular fix because unit tests were failing, but it seems like a good idea that I'm happy to work on.
Describe the solution you'd like
Terraform providers are pinned in tests such that external updates don't cause tests to start failing.
Describe the drawbacks of your solution
We may fall behind new features, but this is only in unit tests so the risk is low.
Describe alternatives you've considered
We could simply do nothing and live with the occasional test failure. I personally feel strongly about working to make tests idempotent and independent of changes in the "outside world", so I think pinning is the right strategy.
The text was updated successfully, but these errors were encountered:
Community Note
Describe the user story
@nitrocode recommended in #4462 (comment) that we pin terraform versions in tests. I didn't want to block that particular fix because unit tests were failing, but it seems like a good idea that I'm happy to work on.
Describe the solution you'd like
Terraform providers are pinned in tests such that external updates don't cause tests to start failing.
Describe the drawbacks of your solution
We may fall behind new features, but this is only in unit tests so the risk is low.
Describe alternatives you've considered
We could simply do nothing and live with the occasional test failure. I personally feel strongly about working to make tests idempotent and independent of changes in the "outside world", so I think pinning is the right strategy.
The text was updated successfully, but these errors were encountered: