Add a concurrency group for generate and deploy

[cam72cam]

Thank you for reporting an issue.

It looks like https://github.com/opentofu/registry/blob/main/.github/workflows/generate-and-deploy.yml could have multiple instances of that job syncing to R2 simultaneously. I don't know if that will cause issues, but it should probably be avoided.

OpenTofu Version

n/a

OpenTofu Configuration Files

// Snippet of HCL that can be used to help reproduce this problem

[tripti-gh]

Can you please assign this issue to me?

[cam72cam]

@tripti-gh sure, please take a look at the other workflow files in the repo for examples.

[vikasrao23]

Hi! I'd like to take ownership of this issue. It looks like the previous assignee (@tripti-gh) hasn't submitted a PR yet.

I plan to add a concurrency: group to all three related workflow files:

• generate-and-deploy.yml
• generate-and-deploy-with-delete.yml
• generate-and-deploy-recent.yml

The full sync workflows (generate-and-deploy and generate-and-deploy-with-delete) would share a single r2-sync concurrency group with cancel-in-progress: false to ensure a running sync is never interrupted. The recent changes workflow would use a separate r2-sync-recent group with cancel-in-progress: true since it runs every 15 minutes and a stale queued run can safely be replaced.

Could you confirm this approach works and whether the accepted label should be added? Happy to submit a PR once confirmed.

[Yantrio]

Sure, I'd love to assign you to this. Please feel free to begin work here. The approach sounds great to me.

[vikasrao23]

Hi @Yantrio! 👋

I've opened PR #3651 with the concurrency group fix as discussed.

The implementation adds:

• r2-sync group (no cancel-in-progress) for full syncs
• r2-sync-recent group (cancel-in-progress: true) for the 15-min recurring sync

This should prevent concurrent R2 writes while allowing queued runs to complete safely.

Let me know if you'd like any adjustments!