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

Stop automatically upgrading module/provider versions #1713

Merged
merged 1 commit into from
Sep 18, 2024
Merged

Stop automatically upgrading module/provider versions #1713

merged 1 commit into from
Sep 18, 2024

Conversation

kieranbrown
Copy link
Contributor

@kieranbrown kieranbrown commented Sep 17, 2024

Please feel free to close this Pull Request if this was an intentional design decision, but I feel as though Digger should not upgrade modules/providers as this can lead to discrepancies when running plans locally vs the CI. Digger should adhere to the project's terraform lock file.

Release Notes

Digger no longer automatically upgrades modules/providers with the `--upgrade` flag when initializing a project. To restore the old behaviour you can use the `extra_args` field to pass `--upgrade` in the plan/apply steps in digger.yaml (https://docs.digger.dev/ce/reference/digger.yml#example-using-all-keys).

@motatoes
Copy link
Contributor

Hi @kieranbrown thanks for filing this! I don't have strong opinions about this, Not sure if there's any case fo having that flag set by users in which case we should make it considerable. Happy to merge this and add a note in release notes about it if users mention that they prefer it we can bring it back with a flag

@kieranbrown
Copy link
Contributor Author

Hi @kieranbrown thanks for filing this! I don't have strong opinions about this, Not sure if there's any case fo having that flag set by users in which case we should make it considerable. Happy to merge this and add a note in release notes about it if users mention that they prefer it we can bring it back with a flag

Hi @motatoes! Thanks for the fast response. I recently came across an issue where I was seeing a difference in planned results locally vs Digger as a result of an upstream provider change. I wasn't seeing this locally because my provider version was locked. I do feel as though the better default behaviour is to have Digger adhere to the lock file.

Do you require me to make any additional changes to support the note in the release notes?

@kieranbrown
Copy link
Contributor Author

@motatoes I've suggested a release note in the PR description - let me know if you require any more changes for this to be merged.

@motatoes
Copy link
Contributor

@kieranbrown many thanks for this, indeed people can add extra args with extra_args, nearly forgot about that 😅

@motatoes
Copy link
Contributor

Failing test is due to missing license key secret missing in fork(unrelated issue), happy to merge this now

@motatoes motatoes merged commit badb6ac into diggerhq:develop Sep 18, 2024
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants