Output of program is not fully printed to the run output

[chtpl]

Select Topic Area

Bug

Body

I have this step in my pipeline:

      - name: "Terraform Plan"
        id: "plan"
        run: |
          cat tfvars.json
          terraform plan -input=false -no-color -var-file="tfvars.json" -out tf-plan.out
        working-directory: environments/${{ inputs.the_env }}

My terraform code seems to have a bug so terraform exits with code 1

[...redacted]
        }
        # (24 unchanged attributes hidden)

        # (3 unchanged blocks hidden)
    }

Plan: 1 to add, 1 to change, 2 to destroy.
Releasing state lock. This may take a few moments...
Error: Terraform exited with code 1.
Error: Process completed with exit code 1.

But the actual error is not present in the logs
On the previous run of the workflow, the error was at least partly printed but still not enough to see the actual error which was like 3 lines long the last time I had a problem with the secrets.

[...redacted]
   }
        # (24 unchanged attributes hidden)

        # (3 unchanged blocks hidden)
    }

Plan: 1 to add, 1 to change, 2 to destroy.
  43: data "azurerm_key_vault_secret" "app_email_client_id" {

module.main.data.azurerm_key_vault_secret.app_email_client_id: Still reading... [20s elapsed]
Error: Terraform exited with code 1.
Error: Process completed with exit code 1.

So I don't know what the actual error is and can't resolve it

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐