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

security_policy resource: use PID for filename instead of random #2368

Merged
merged 2 commits into from
Dec 4, 2017

Conversation

jquick
Copy link
Contributor

@jquick jquick commented Dec 4, 2017

There is an issue with the security policy when used with the new Train caching. Since it creates a unique export name every call it will not be cached. This change was originally created to protect from parallel runners. Moving it to Process.pid will allow it to be cached as well as protect from parallel runners.

Signed-off-by: Jared Quick jquick@chef.io

Signed-off-by: Jared Quick <jquick@chef.io>
@jquick jquick requested a review from a team as a code owner December 4, 2017 19:35
@jerryaldrichiii
Copy link
Contributor

Excellent catch @jquick!

@jquick jquick force-pushed the jq/security_policy_uniq_pid branch from ef7c49f to c0ac3ed Compare December 4, 2017 19:56
Signed-off-by: Jared Quick <jquick@chef.io>
@jquick jquick force-pushed the jq/security_policy_uniq_pid branch from c0ac3ed to afb149f Compare December 4, 2017 20:10
@adamleff adamleff changed the title Update security policy export to use pid instead of random. security_policy resource: use PID for filename instead of random Dec 4, 2017
@adamleff adamleff added the Type: Bug Feature not working as expected label Dec 4, 2017
@adamleff adamleff merged commit 4b1c1b0 into master Dec 4, 2017
@adamleff adamleff deleted the jq/security_policy_uniq_pid branch December 4, 2017 20:31
@arlimus
Copy link
Contributor

arlimus commented Dec 5, 2017

Thank you for fixing this @jquick !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Feature not working as expected
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants