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

Support sensitive #781

Merged
merged 10 commits into from
Jan 18, 2020
Merged

Support sensitive #781

merged 10 commits into from
Jan 18, 2020

Conversation

rodjek
Copy link
Owner

@rodjek rodjek commented Jan 14, 2020

Rebasing #464 in preparation for the 2.8.0 release (can no longer push to the original PR for some reason).

Closes #464

@rodjek rodjek added this to the 2.8.x milestone Jan 14, 2020
@coveralls
Copy link

coveralls commented Jan 14, 2020

Coverage Status

Coverage increased (+0.1%) to 85.646% when pulling 93ea7f3 on support-sensitive into 290f12a on master.

@rodjek rodjek merged commit ffa754a into master Jan 18, 2020
@rodjek rodjek deleted the support-sensitive branch January 18, 2020 21:28
alexjfisher added a commit to alexjfisher/puppet-chrony that referenced this pull request Jul 15, 2020
2.7.9 contains rodjek/rspec-puppet#781 and that
appears to have broken our tests.  Fix was pretty simple, but not sure
the rspec-puppet PR was meant to break existing test suites like this.
@DavidS DavidS added the feature label Oct 27, 2020
alexjfisher added a commit to alexjfisher/puppet-chrony that referenced this pull request Nov 16, 2020
2.7.9 contained rodjek/rspec-puppet#781 and that
broke our tests.

2.7.9 was pulled from rubygems, but this breaking change is back in
2.8.0 :(
kenyon pushed a commit to voxpupuli/puppet-chrony that referenced this pull request Nov 16, 2020
2.7.9 contained rodjek/rspec-puppet#781 and that
broke our tests.

2.7.9 was pulled from rubygems, but this breaking change is back in
2.8.0 :(
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants