So my nixpkgs moved, and thus I have slightly newer providers or whatnot available than are in my lock file.
Cool, if only I had any idea what to do in this situation:
I try to run terraform init:
+ /nix/store/187rmzs3cw0h8g6sklyvl3fxfsxh9gkh-terraform-1.10.3/bin/terraform init
Initializing the backend...
Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider
│ hashicorp/aws: the previously-selected version 5.72.0 is no longer
│ available
│
│ To see which modules are currently depending on hashicorp/aws and
│ what versions are specified, run the following command:
│ terraform providers
╵
so I try to run terraform providers:
+ /nix/store/187rmzs3cw0h8g6sklyvl3fxfsxh9gkh-terraform-1.10.3/bin/terraform providers
╷
│ Error: Required plugins are not installed
│
│ The installed provider plugins are not consistent with the packages
│ selected in the dependency lock file:
│ - registry.terraform.io/hashicorp/aws: there is no package for registry.terraform.io/hashicorp/aws 5.72.0 cached in .terraform/providers
│
│ Terraform uses external plugins to integrate with a variety of
│ different infrastructure services. To download the plugins required
│ for this configuration, run:
│ terraform init
╵
I feel like I’m getting TROLLED and not in a fun way.
Could terraform PLEASE possibly give actual remediation instructions in this case? Please? It’s been years of this sort of thing and every time it’s been just long enough since I’ve touched it that I’m nervous to mess up my state and completely lost on what the easy thing to do is. Surely there’s an easy solution to this extremely commonplace thing. Is it just lore that everyone knows and doesn’t bother putting in the CLI? Am I missing something terribly obvious?