Set null_resource_count to 1

[austinsonger]

Updated null_resource_count to 1 to trigger Terrateam.

[Copilot]

Pull Request Overview

This PR updates the null_resource_count parameter from 0 to 1 in the dev environment configuration to trigger Terrateam operations.

• Updated null_resource_count parameter value to 1

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[austinsonger]

terrateam apply

[terrateam-action]

Potentially Stale Operations Detected

Terrateam has identified potentially stale operations whose current status cannot be determined. This occurs when GitHub fails to provide status updates. These are blocking the execution of this operation.

What to Do Next

• If the operations are still in progress, no immediate action is necessary. This operation will run automatically when they complete.
• If the operations have encountered failures, follow the instructions below to unlock them, this operation will resume automatically.

Potentially Stale Operations

Pull Request	Operation	State	Created At
#1	Plan	Running	2025-10-3 21:30 UTC

If these appear to be stuck, unlock them by commenting in any pull request:

terrateam unlock 1

Be careful when unlocking. Make sure that these runs are actually stuck by verifying if there are any running GitHub Actions workflows.

If this persists, verify the GitHub Action workflow matches the documentation.

For further support:

• Join our Slack community (Fastest)
• Email us directly at support@terrateam.io

[terrateam-action]

Missing Plans ✖️

Cannot perform apply due to missing plans for the following directory and workspaces:

Dir	Workspace
dev	default

Plans are necessary to perform an apply. In order to create all plans necessary to apply this change, comment the following:

terrateam plan