-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Best Practice to perform Module Upgrades #2995
Comments
Maybe - its not something we have tried or documented |
ok, I do understand that every team has it own way to perform the upgrades. As my env uses 17.0.0 modules, i.e pretty stable thanks the community's collective efforts. Which is not included in this module 17.0.0. I prefer to upgrade the module to 18.0.0. Basically, am I wrong or am I terribly wrong thinking this way? |
Absolutely you can skip the version but it is always good to practice systematic approach. While changing from version 17.0.0 to version 20.0.0, Terraform will use it directly if you mention in the configuration. , it is always important to keep trace of changes in each version to avaoid compatibility issues . |
This issue has been automatically marked as stale because it has been open 30 days |
This issue was automatically closed because of stale in 10 days |
Hey All,
Need to clarify few things
The text was updated successfully, but these errors were encountered: