We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would it be hard to make it an option to use either git or s3 (or other) for storing the lock files?
The text was updated successfully, but these errors were encountered:
Git should be doable and only requires lines like this to be changed:
gh-action-mutex/rootfs/scripts/lock.sh
Line 17 in 4b87e07
S3 is a completely different mechanism and would require a lot more work.
Though personally I don’t need both use cases and would rely on external contribution and testing :)
Sorry, something went wrong.
Quick thought: Terraform's S3 backend relies on DynamoDB for locking. Perhaps S3 doesn't have the facilities to support atomic locking?
No branches or pull requests
Would it be hard to make it an option to use either git or s3 (or other) for storing the lock files?
The text was updated successfully, but these errors were encountered: