Can I debug what's going on when terraform-plan sends an empty diff to PR?

[wolverian]

This is what the action comments with to the PR:

Terraform plan in __infra__
```

```
Plan generated in [Terraform #13](https://github.com/XXXX/XXXX/actions/runs/XXXX)

Looking in the Action log, we can see the plan was actually output:

2022-02-09T13:02:10.3043635Z 
2022-02-09T13:02:10.4229560Z Reading latest terraform version
2022-02-09T13:02:10.7142412Z Downloading https://releases.hashicorp.com/terraform/1.1.5/terraform_1.1.5_linux_amd64.zip to terraform_1.1.5_linux_amd64.zip
2022-02-09T13:02:10.7147426Z Downloading ...
2022-02-09T13:02:10.8353753Z 18748879 bytes downloaded.
2022-02-09T13:02:11.4253767Z Switched terraform to version "1.1.5" 
2022-02-09T13:02:11.4587390Z 
2022-02-09T13:02:11.4588149Z �[0m�[1mInitializing the backend...�[0m
2022-02-09T13:02:12.4180460Z �[0m�[32m
2022-02-09T13:02:12.4180852Z Successfully configured the backend "s3"! Terraform will automatically
2022-02-09T13:02:13.6621989Z use this backend unless the backend configuration changes.�[0m
2022-02-09T13:02:13.6622236Z 
2022-02-09T13:02:13.6622472Z �[0m�[1mInitializing provider plugins...�[0m
2022-02-09T13:02:13.6622928Z - Reusing previous version of hashicorp/aws from the dependency lock file
2022-02-09T13:02:13.7979490Z - Reusing previous version of hashicorp/tls from the dependency lock file
2022-02-09T13:02:13.9616201Z - Installing hashicorp/aws v3.74.1...
2022-02-09T13:02:18.4616400Z - Installed hashicorp/aws v3.74.1 (signed by HashiCorp)
2022-02-09T13:02:18.5669509Z - Installing hashicorp/tls v3.1.0...
2022-02-09T13:02:18.9921570Z - Installed hashicorp/tls v3.1.0 (signed by HashiCorp)
2022-02-09T13:02:18.9924782Z 
2022-02-09T13:02:18.9930041Z Terraform has made some changes to the provider dependency selections recorded
2022-02-09T13:02:18.9930569Z in the .terraform.lock.hcl file. Review those changes and commit them to your
2022-02-09T13:02:18.9931037Z version control system if they represent changes you intended to make.
2022-02-09T13:02:18.9931324Z 
2022-02-09T13:02:18.9932100Z �[0m�[1m�[32mTerraform has been successfully initialized!�[0m�[32m�[0m
2022-02-09T13:02:26.5451036Z 
2022-02-09T13:02:26.5451537Z Terraform used the selected providers to generate the following execution
2022-02-09T13:02:26.5451937Z plan. Resource actions are indicated with the following symbols:
2022-02-09T13:02:26.5452190Z   + create
2022-02-09T13:02:26.5452328Z 
2022-02-09T13:02:26.5452453Z Terraform will perform the following actions:
2022-02-09T13:02:26.5452610Z 
2022-02-09T13:02:26.5459563Z   # aws_route53_record.XXXXXX will be created
2022-02-09T13:02:26.5465130Z   + resource "aws_route53_record" "XXXXXX" {
2022-02-09T13:02:26.5465472Z       + allow_overwrite = (known after apply)
2022-02-09T13:02:26.5465758Z       + fqdn            = (known after apply)
2022-02-09T13:02:26.5466062Z       + id              = (known after apply)
2022-02-09T13:02:26.5466760Z       + name            = "XXXXXX"
2022-02-09T13:02:26.5467129Z       + type            = "TXT"
2022-02-09T13:02:26.5467391Z       + zone_id         = "XXXXXX"
2022-02-09T13:02:26.5467619Z     }
2022-02-09T13:02:26.5467744Z 
2022-02-09T13:02:26.5467869Z Plan: 1 to add, 0 to change, 0 to destroy.
2022-02-09T13:02:29.8781527Z Post job cleanup.

Is there a way to debug what's going on when this kind of an issue happens?

[dflook]

Hello @wolverian, you can enable debug logging by setting the ACTIONS_STEP_DEBUG secret to true.

Please create an issue which includes your workflow yaml.

[wolverian]

Thank you! 👍