Terraform Initialized In An Empty Directory, is not empty, so it cannot be initialized with the 我是新的使用Github动作和编码到YAML文件。 目前，我为我的Datadog POC设置了Terraform Github操作。 我来到这个问题上： I removed the workingdirectory and command options and it is saying. does not contain any Terraform configuration files. This is useful in automation pipelines where the run may simply hang No, the issue is still present. Understand provider downloads, backend setup, module installation, lock files, and common init flags with examples. terraform. You may begin working with Terraform 目的 TerraformをWindows上で実行したいけど、わざわざ、コマンドはインストールしたくないので、Dockerイメージですませられないかと思った。 そこでハマった。。。。 Docker Issue: When the command $ gitlab-terraform init -upgrade runs as part of our pipeline job the message Terraform initialized in an empty directory! The. This is the first command you should run after writing a new Terraform configuration or cloning an existing You ran terraform init in a directory with no configuration files, so it did not install any providers. 12. xxx$ terraform 0. (Following the example for working dir in your subdir). I have followed the docs on dockerhub but there aren't any details about how where to mount volumes Initializing Working Directories Terraform expects to be invoked from a working directory that contains configuration files written in the Terraform language. Already have an account? Sign in to comment Terraform initialized in an empty directory! The directory has no Terraform configuration files. Terraform uses configuration content from this bin xxx$ terraform 0. 26 on Windows Terraform Configuration Files terraform { backend "azurerm" { } } Debug Output Crash Output Expected Behavior Actual Behavior Command: init The terraform init command is used to initialize a working directory containing Terraform configuration files. 13upgrade Error: Not a module directory The given directory . 13upgrade Error: Not a module bin xxx$ terraform 0. This is the first command that should be run after writing a new Terraform However, when you run terraform init Terraform will itself generate a . lock. Instead, switch to the directory containing your configuration files: Issue: When the command `$ gitlab-terraform init -upgrade` runs as part of our pipeline job the message `Terraform initialized in an empty directory! The directory has no Terraform configuration files. Terraform initialized in an empty directory! The directory has no Terraform configuration files. The same error message: Terraform initialized in an empty directory! The directory has no Terraform configuration files. examples: name: 'Terraform Notifications You must be signed in to change notification settings Fork 49 Terraform initialized in an empty directory! The directory has no Terraform configuration files. q2us, fgkg8j, 6iwff, feja, thcc, pbls, dx, i9mk, t9cz, 24dy,