Fix: pending SystemCertPool() deprecation#61
Conversation
In docker/go-connections/tlsconfig this method has become deprecated causing dependency bumps to fail. Switching to the recommended `crypto/x509` method instead.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe pull request modifies the TLS configuration in the HTTP client setup. Specifically, the system CA certificate pool is now obtained directly from the standard library's 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the Docker CPI TLS setup to avoid the deprecated docker/go-connections/tlsconfig.SystemCertPool() API by switching to the standard library crypto/x509.SystemCertPool().
Changes:
- Replace
dkrtlsconfig.SystemCertPool()withx509.SystemCertPool()in the CPI HTTP client TLS configuration. - Add the
crypto/x509import to support the new call.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
In docker/go-connections/tlsconfig this method has become deprecated causing dependency bumps to fail. Switching to the recommended
crypto/x509method instead.Fixes:
^ https://bosh.ci.cloudfoundry.org/teams/main/pipelines/bosh-docker-cpi/jobs/bump-deps/builds/92#L69ba586e:224:225