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 to pdk 3, ruby 3 #778

Merged
merged 5 commits into from
Dec 18, 2024
Merged

upgrade to pdk 3, ruby 3 #778

merged 5 commits into from
Dec 18, 2024

Conversation

rrotter
Copy link
Member

@rrotter rrotter commented Dec 17, 2024

Upgrade to:

  • ruby 3.2: used in current puppet 8
  • pdk 3.3.0 (latest that doesn't cause gem conflicts)
  • pdk template 3.0.1 (later versions change rake spec tasks significantly introducing a ton of warnings)
  • add standardrb this will be another PR

@rrotter rrotter force-pushed the pdk_prep branch 2 times, most recently from c8dd2e5 to 209aa95 Compare December 17, 2024 22:10
@rrotter rrotter changed the title pdk upgrade prep upgrade to pdk 3, ruby 3 Dec 17, 2024
@rrotter rrotter requested review from daaang and botimer December 17, 2024 22:16
@rrotter rrotter marked this pull request as ready for review December 17, 2024 22:18
@rrotter rrotter force-pushed the pdk_prep branch 2 times, most recently from fa427ea to f53e3e6 Compare December 17, 2024 22:42
@rrotter
Copy link
Member Author

rrotter commented Dec 17, 2024

Removed the last commit in this PR (which added standardrb), it doesn't belong here.
[edit: standardrb moved to #779]

asdf is a local developer tool, so its config doesn't belong in git.
OTOH, .ruby-version may be used by CI so it will remain.
- ruby 3.2 is the current ruby in puppet 8
- pdk 3.2 introduces regressions in CI
- Intentional differences from pdk template:
  - don't include rake release tasks
  - don't include `networking` default facts
  - remove rubocop config
@rrotter rrotter merged commit 785d577 into production Dec 18, 2024
2 of 3 checks passed
@rrotter rrotter deleted the pdk_prep branch December 18, 2024 17:09
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