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

Ruby 2.7? #21

Open
cobbr2 opened this issue Jul 25, 2024 · 6 comments
Open

Ruby 2.7? #21

cobbr2 opened this issue Jul 25, 2024 · 6 comments

Comments

@cobbr2
Copy link

cobbr2 commented Jul 25, 2024

Is there any interest, or has anybody, gotten this gem to work with Ruby 2.7? We have an urgent need to migrate to MSK IAM, but we also have an app that hasn't been ported to Ruby 3 that has a lot of dependencies we haven't worked through.

@bruce-szalwinski-he
Copy link
Owner

I haven't tried to build against Ruby 2.7. I needed MSK IAM for a cluster shared across accounts. And we pair it with the karafka tool chain for kafka processing. As the karafka framework only support Ruby >= 3.0.0, I didn't invest any time in trying versions less than 3.

@bruce-szalwinski-he
Copy link
Owner

The ci workflow does build against many different Ruby versions. You could create a PR, add 2.7 to the matrix and see what dragons be out there.

@cobbr2
Copy link
Author

cobbr2 commented Jul 25, 2024

Thanks, Bruce. We also use karafka, but an older version (2.2.6). I like your idea, thanks.

@bruce-szalwinski-he
Copy link
Owner

I had a great time working with Maciej Mensfeld , maintainer of all things karafka, to add OAuth Bearer Auth support to the karafka tool chain. From the release notes, it looks like OAuth support was released at the same time 2.7 was dropped.

@cobbr2
Copy link
Author

cobbr2 commented Jul 25, 2024

Thanks, @bruce-szalwinski-he . We may be between a rock & a hard place. I'll reach out to Mr. Mensfeld as an issue in karafka. I'll keep this issue open until we know our path forward, if you don't mind.

@bruce-szalwinski-he
Copy link
Owner

@cobbr2 - did you figure out a way forward? Can this issue be closed?

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

No branches or pull requests

2 participants