Conversation
patrickdappollonio
left a comment
There was a problem hiding this comment.
I'm not sure we want to hard pin the versions to specific ones. I would think a version "range" of anything within major and minor should suffice (I saw in the past we had just major, but considering minor versions could have some breaking changes, I wouldn't risk it).
Can we do it in ranges? For example for the cloud-nat module, I would prefer ~> 5.3 rather than hardcoding to 5.3.0.
mrsimonemms
left a comment
There was a problem hiding this comment.
I'm in agreement with @patrickdappollonio on this and would prefer to see a range dependency used. If there is a minimum requirement on a specific version for something, you can keep the range but bump the min version.
If there is a reason this won't work, please explain it so I can understand it.
Co-authored-by: Simon Emms <simon@simonemms.com>
|
@mrsimonemms @patrickdappollonio,i have applied according changes can i get a ✅ :) |
Requested changes made
Description
Updated Terraform modules to resolve provider version conflicts:
10.0.05.3.0Before Updating



After Updating



Testing
Provision Google management with the flag
--gitops-template-branch fix-gke-versionExample: