It would be great to support auto-queue-runs in the upload-configuration action so it is possible to queue runs similar to how the version control driven setting in Terraform Cloud. This is for cases where we do not want a branch to automatically apply but want the run queued in Terraform Cloud (which is not the same as a saved plan). Right now a non-speculative plan will fail in create-run if another run is already queued for apply but not applied yet since it has the lock. This is not quite the same as how the version control driven setting works where a new plan will queue behind the one with the lock.
It would be great to support auto-queue-runs in the upload-configuration action so it is possible to queue runs similar to how the version control driven setting in Terraform Cloud. This is for cases where we do not want a branch to automatically apply but want the run queued in Terraform Cloud (which is not the same as a saved plan). Right now a non-speculative plan will fail in create-run if another run is already queued for apply but not applied yet since it has the lock. This is not quite the same as how the version control driven setting works where a new plan will queue behind the one with the lock.