@@ -184,32 +184,3 @@ Path supports template syntax. This allows for separation of logs while accounti
184
184
- ` ppid ` - parent process ID (typically editor's or editor plugin's PID)
185
185
186
186
The path is interpreted as [ Go template] ( https://golang.org/pkg/text/template/ ) , e.g. ` /tmp/terraform-ls-memprofile-{{timestamp}}.log ` .
187
-
188
- ## "No root module found for ... functionality may be limited"
189
-
190
- Most of the language server features depend on initialized root modules
191
- (i.e. folder with ` *.tf ` files where you ran ` terraform init ` successfully).
192
- and server's ability to discover them within the hierarchy and match them
193
- with files being open in the editor.
194
-
195
- This functionality should cover many hierarchies, but it may not cover yours.
196
- If it appears that root modules aren't being discovered or matched the way
197
- they should be, it can be useful to use ` inspect-module ` to obtain
198
- the discovery results and provide them to maintainers in a bug report.
199
-
200
- Point it to the same directory that you tried to open in your IDE/editor
201
- and wait for the output - it may take some seconds or low minutes
202
- depending on the complexity of your hierarchy and number of root modules in it.
203
-
204
- ```
205
- $ terraform-ls inspect-module /path/to/dir
206
- ```
207
-
208
- ## "Unable to retrieve schemas for ..."
209
-
210
- The process of obtaining the schema currently requires access to the state,
211
- which in turn means that if the code itself doesn't have enough context
212
- to obtain the state and/or there isn't context available from config file(s)
213
- in standard locations you may need to provide that extra context.
214
-
215
- See https://github.com/hashicorp/terraform-ls/issues/128 for more.
0 commit comments