Ask to terraform init an uninitialized workspace

[paultyng]

https://microsoft.github.io/language-server-protocol/specification#window_showMessageRequest

The show message request is sent from a server to a client to ask the client to display a particular message in the user interface. In addition to the show message notification the request allows to pass actions and to wait for an answer from the client.

Not entirely sure about the UX on this, but may be worth exploring.

[paultyng]

We should probably ask to initialize entirely uninitialized workspaces or when we get that error from the Terraform binary. But we may be able to be a bit proactive about it, when there are providers in source that are not initialized or maybe the local mirror directories change, etc.

[radeksimko]

I think this might require some help from the language server in relation to #32 because the server will likely be the one that knows better/best where it's suitable to terraform init a particular directory.

[BertelBB]

Is it possible to disable the initialization?
It is breaking the hashicorp.terraform extension for me because I am opening a workspace in VSCode with multiple Terraform projects and the extension is trying to perform the initialization in the root directory of the workspace, which is not a Terraform project.

[radeksimko]

The error will not be reported as per #171 from the next release (0.4.0; to be released in coming days). The schema is still necessary for most functionality (pretty much all except formatting), but we need to better understand where in the hierarchy could a folder be potentially initd, so we can hint this to the user - as opposed to just expect it in any directory that is being opened - that's what this issue is mainly about.

Supporting monorepo and other more complex hierarchies is something we plan to support as part of #32

[radeksimko]

As for the implementation details of this one, I realized that the JSON RPC library we use doesn't seem to support server->client requests. It can only send notifications (without waiting for response), such as window/showMessage via jrpc2.ServerPush().

(I tried sending showMessage to the client, which displayed the message in the UI, but showMessageRequest did nothing)

[ghost]

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 context necessary to investigate further.