Skip to content
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

Open
devops-inthe-east opened this issue Mar 29, 2024 · 4 comments
Open

Best Practice to perform Module Upgrades #2995

devops-inthe-east opened this issue Mar 29, 2024 · 4 comments

Comments

@devops-inthe-east
Copy link

Hey All,

Need to clarify few things

  1. Can I skip module versions when upgrading a specific modules.
  2. Like moving from 17.0.0 to 20.0.0
@bryantbiggs
Copy link
Member

Maybe - its not something we have tried or documented

@devops-inthe-east
Copy link
Author

devops-inthe-east commented Mar 29, 2024

ok,

I do understand that every team has it own way to perform the upgrades.
However is it safe to assume that upgrading one major version at a time is ideal.

As my env uses 17.0.0 modules, i.e pretty stable thanks the community's collective efforts.
However, since Launch Configuration are Deprecated and being replaced with Launch Templates.

Which is not included in this module 17.0.0. I prefer to upgrade the module to 18.0.0.
However there are some breaking change.
So I considered to skip this module and preferred the latest one to upgrade.

Basically, am I wrong or am I terribly wrong thinking this way?

@170031284
Copy link

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 .

Copy link

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants