-
Notifications
You must be signed in to change notification settings - Fork 85
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
Add Puppetserver catalog v4 API support #228
Conversation
996e85c
to
452059f
Compare
I re-ran the CI job and it passed. I don't know why the results are not updating above, but you can see the results here: https://github.com/seanmil/octocatalog-diff/actions/runs/372918628 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much for this - its a lot of work, and I appreciate you bringing octocatalog-diff into the modern era!
I had a few questions, mainly because I'm just not as familiar with modern puppet.
spec/octocatalog-diff/tests/cli/options/puppet_master_token_file_spec.rb
Outdated
Show resolved
Hide resolved
Co-authored-by: Andrew Hayworth <ahayworth@github.com>
…le_spec.rb Co-authored-by: Andrew Hayworth <ahayworth@github.com>
Update docs per feedback provided by Andrew Hayworth in the PR.
This is excellent - thank you so much for the contributions 😄 |
Overview
This pull request introduces support for the Puppetserver v4 catalog API, introduced in Puppetserver 6.3.0.
This new API endpoint offers additional capabilities and options not present in earlier API versions. In particular, updating facts and catalogs with PuppetDB as part of the compile is now optional. For Puppet Enterprise customers, you may use PE RBAC tokens to authenticate for v4 catalog compiles.
Checklist
rake
in your checkout directory, or review the CI job triggered whenever you push to a pull request.rake coverage:spec
or ignoring untestable sections of code with# :nocov
comments. If you need help getting to 100% coverage please ask; however, don't just submit code with no tests..gem
file into the vendor/cache directory.