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

Compliance Token resource #91

merged 3 commits into from Sep 13, 2016


None yet
4 participants

jeremymv2 commented Sep 12, 2016


This PR introduces compliance_token resource.
The goal is to have a self-contained resource for storing the Compliance Server token and exchanging the refresh_token for an access token, if needed.

The compliance_token resource stashes the token in Chef's node.run_state hash. The token can then be passed between resources, and evaluated during the execution phase. run_state is always discarded at the end of the chef-client run.

Issues Resolved


Check List


This comment has been minimized.


jeremymv2 commented Sep 12, 2016

Another intent I have for this change is so that we can add an upload.rb recipe and not have to duplicate the existing ruby_block 'exchange_refresh_token' in each recipe.

@jeremymv2 jeremymv2 referenced this pull request Sep 12, 2016


profile upload #92

2 of 4 tasks complete

@chris-rock chris-rock merged commit caf1d0c into chef-cookbooks:master Sep 13, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed

@iennae iennae removed the in progress label Sep 13, 2016


This comment has been minimized.


chris-rock commented Sep 13, 2016

Great improvement @jeremymv2

@jeremymv2 jeremymv2 deleted the jeremymv2:exchange_refresh_token branch Sep 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment