cloudposse / cloudposse/atmos

Stale providers in a `.terraform.lock.hcl` file can cause issues

Open
#105 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
1.4k
Forks
175
Avg merge
2d 3h
Merged PRs (30d)
134

Description

Found a bug? Maybe our [Slack Community](https://slack.cloudposse.com) can help.

[![Slack Community](https://slack.cloudposse.com/badge.svg)](https://slack.cloudposse.com)

## Describe the Bug
Sometimes old providers are cached in a `.terraform.lock.hcl` file and need to be manually removed to allow upgrading modules.

It would be nice to have an `atmos.yaml` setting to remove a component's `.terraform.lock.hcl` (without running a full clean) prior to running a `terraform init`. So if this setting was enabled, and a plan/deploy/apply was run, it would first remove the lock file, then run the init, and then the desired command.

or just always run `terraform init -upgrade`

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.