Skip to content
New issue

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

Make writing the env deployment file close to atomic #1039

Merged
merged 1 commit into from
Mar 12, 2020

Conversation

binford2k
Copy link
Contributor

This isn't quite atomic, but it's really close. And AFAIK, it's as close
as we can get to atomic in pure Ruby since flock is advisory.

Fixes #813

This isn't quite atomic, but it's really close. And AFAIK, it's as close
as we can get to atomic in pure Ruby since `flock` is advisory.

Fixes puppetlabs#813
@binford2k binford2k requested a review from a team March 11, 2020 23:24
Copy link
Contributor

@adrienthebo adrienthebo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

flock is advisory, but if it's r10k fighting with itself it might still be handy.

That said we do need a better story about not running r10k in parallel.

@adrienthebo adrienthebo merged commit 5029fd4 into puppetlabs:master Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Writing .r10k-deploy.json is not atomic
4 participants