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

Upgrade PDK Preparation #773

Merged
merged 4 commits into from
Dec 13, 2024
Merged

Upgrade PDK Preparation #773

merged 4 commits into from
Dec 13, 2024

Conversation

rrotter
Copy link
Member

@rrotter rrotter commented Dec 12, 2024

All tests passing without puppet-rspec-utils. Running bundle exec pdk update at this point results in a clean upgrade that can run rake spec successfully on ruby 2.7 and 3.2. I'll put the actual upgrade and any rubocop/lint cleanup in another PR.

- add PDK 2 to Gemfile
- don't track Gemfile.lock
- rearrange .gitignore to be closer to what PDK generates
- add .sync.yml to correctly generate:
  - .gitignore
  - Gemfile
  - default_facts.yml
@rrotter rrotter force-pushed the upgrade_pdk2 branch 5 times, most recently from 765a50c to bcd883d Compare December 13, 2024 04:52
@rrotter rrotter changed the title Upgrade PDK Upgrade PDK Preparation Dec 13, 2024
@rrotter rrotter marked this pull request as ready for review December 13, 2024 05:58
@rrotter rrotter requested a review from daaang December 13, 2024 14:37
Copy link
Collaborator

@daaang daaang left a comment

Choose a reason for hiding this comment

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

+124 –448

–324 feels good

removed mocks were not actually used in any specs
- replace all remaininng rspec-puppet-utils mocks
- remove rspec-puppet-utils from Gemfile
@rrotter rrotter merged commit 637c417 into production Dec 13, 2024
1 check passed
@rrotter rrotter deleted the upgrade_pdk2 branch December 13, 2024 15:46
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.

2 participants