Update webhook ruby to 3.2

christinach commented 3 weeks ago

What maintenance needs to be done?

We're using ruby 2.7 in Lambda AWS. We should update to 3.2 or 3.3

Level of urgency

[x] High
[ ] Moderate
[ ] Low

EOL upgrade

[ ] EOL Date MM/DD/YYYY

Why is this maintenance needed?

A clear description of why this is needed.

Acceptance criteria

[x] Update webhook to ruby 3.2
[x] Deploy on aws alma staging webhook
[x] Deploy bibdata to staging
[x] Trigger an incremental in the alma sandbox. Make that when it finishes bibdata has fetched the data and indexed them.
[ ] Deploy on aws alma production webhook

Implementation notes, if any

See Webhook readme notes

I attempted to deploy with Ruby 3.1 but failed because it supports only ruby 3.2 and 3.3

christinach commented 2 weeks ago

AWS staging webhook does not receive messages with ruby v 2.7 or 3.2. First I need to see why this is happening.

christinach commented 2 weeks ago

AWS staging webhook does not receive messages with ruby v 2.7 or 3.2. First I need to see why this is happening.

I was able to resolve an error that I could see after the various deploys. It was an incompatibility between the gems and the new version of ruby 3.2 I had deployed in combination with a stale datadog layer from ruby 2.7.

@mzelesky thank you for helping me testing this by editing records patiently every time I asked you! Also thank you for reviewing numerous times with me the Alma configuration settings in the sandbox to ensure they were correct after the cloning of the Alma sandbox.

The files are in bibdata-staging

pulibrary / bibdata