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

(CAT-1222) - Require puppetlabs-rspec-puppet over rspec-puppet #415

Merged
merged 1 commit into from
Oct 18, 2023

Conversation

jordanbreen28
Copy link
Contributor

Summary

this PR requires the newer puppetlabs-rspec-puppet (official puppet supported) over rspec-puppet. (no longer officially supported by puppet).

Additional Context

Add any additional context about the problem here.

  • Root cause and the steps to reproduce. (If applicable)
  • Thought process behind the implementation.

Related Issues (if any)

Mention any related issues or pull requests.

Checklist

  • 🟢 Spec tests.
  • 🟢 Acceptance tests.
  • Manually verified.

@jordanbreen28 jordanbreen28 marked this pull request as draft October 18, 2023 10:50
@jordanbreen28 jordanbreen28 force-pushed the CAT-1222-require_puppetlabs-rspec-puppet branch 3 times, most recently from b0858db to f41dc6e Compare October 18, 2023 10:53
this commit requires the newer puppetlabs-rspec-puppet (official
puppet supported) over rspec-puppet. (no longer puppet supported)
@jordanbreen28 jordanbreen28 force-pushed the CAT-1222-require_puppetlabs-rspec-puppet branch from f41dc6e to 1f6c13e Compare October 18, 2023 10:55
@jordanbreen28 jordanbreen28 marked this pull request as ready for review October 18, 2023 10:56
Copy link
Contributor

@LukasAud LukasAud left a comment

Choose a reason for hiding this comment

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

LGTM

@LukasAud LukasAud merged commit 22add37 into main Oct 18, 2023
6 checks passed
@LukasAud LukasAud deleted the CAT-1222-require_puppetlabs-rspec-puppet branch October 18, 2023 11:00
@bastelfreak
Copy link
Collaborator

@LukasAud should we mark this as breaking change or is it only a feature? (I'm unsure but tend to to breaking change).

@jordanbreen28
Copy link
Contributor Author

@bastelfreak I actually agree, breaking change is more appropriate. Will update.

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

Successfully merging this pull request may close these issues.

3 participants