providers/terraform: remote state data source supports backends #12173
Conversation
| backendlegacy "github.com/hashicorp/terraform/backend/legacy" | ||
| backendlocal "github.com/hashicorp/terraform/backend/local" | ||
| backendconsul "github.com/hashicorp/terraform/backend/remote-state/consul" | ||
| backendinmem "github.com/hashicorp/terraform/backend/remote-state/inmem" |
There was a problem hiding this comment.
not to block this PR, but I wonder if we need some general refactoring/cleanup regarding around the backend packages. some of these import blocks are getting messy.
There was a problem hiding this comment.
I don't think so since its no different than our internal_plugin_list.go file. That file happens to be generated now (it used to not!), but its just like this. The full list of built-in things has to be enumerated somewhere and backend/init is where that's happening. I think as long as we do this only in one place we're good to go, cause its going to happen somewhere anyways.
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
This changes the
terraform_remote_statedata source to support backends rather than going through the legacy remote state interface.To support this change without duplicating the list of backends, I introduce a new package
backend/initwhich simply provides an API for looking up backend initializers. Thecommandpackage was changed to use this as well. This means that we have a uniform way to lookup and initialize a backend.