You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user may not start with initialized root modules and therefore they won't be discovered by the server.
Instinctively though users will follow the error message and try to terraform init while keeping the editor open. The server however won't detect these new files and won't load the schema from the newly initialized root module automatically.
The server only detects changes for now.
Attempted Solutions
Restart editor/server.
Proposal
Identifying prospective root modules is difficult - in theory any folder with *.tf files, or even without may become a root module and be init-ed in the future.
We could however track prospective root modules by tracking any directory of a file which is received via didOpen, so we'd only actively track the folders of files which are currently open.
The text was updated successfully, but these errors were encountered:
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.
ghost
locked as resolved and limited conversation to collaborators
Mar 4, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current Version
Use-cases
The user may not start with initialized root modules and therefore they won't be discovered by the server.
Instinctively though users will follow the error message and try to
terraform init
while keeping the editor open. The server however won't detect these new files and won't load the schema from the newly initialized root module automatically.The server only detects changes for now.
Attempted Solutions
Restart editor/server.
Proposal
Identifying prospective root modules is difficult - in theory any folder with
*.tf
files, or even without may become a root module and beinit
-ed in the future.We could however track prospective root modules by tracking any directory of a file which is received via
didOpen
, so we'd only actively track the folders of files which are currently open.The text was updated successfully, but these errors were encountered: