You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Redis clusters for the Exhibits site are at version 5.0.0 and should be upgraded soon. This version is not scheduled for EOL but the service has been updated to 5.0.6 and those updates should be applied.
Longer term, this service should be updated to at least 6.x and ideally (AWS recommendation) to 7.x to get completely up to date. It might be easier to update all the way, all at once or it might be easier to update minimally until we reach a future EOL date.
The text was updated successfully, but these errors were encountered:
We are stable in terms of EOL but we are still at 5.0.6 across the Library. This is something we could address in the next sprint, but there's no rush.
I think the heavy lifting for this one is Greg, but I'm happy to help support in any way I can - I don't think there's any blockers on my end unless we're trying to not make too many infrastructure changes pre-joyce release in september.
That said, I think getting off elastic beanstalk (i.e. moving to containers) might be higher priority? Hoping we can start to talk through what that would actually look like in our next non-joyce focused spotlight sprint. I'd also really like to get that roadmap planning going when we can (I think that's scheduled for September still), so we can better prioritize things like this.
The Redis clusters for the Exhibits site are at version 5.0.0 and should be upgraded soon. This version is not scheduled for EOL but the service has been updated to 5.0.6 and those updates should be applied.
Longer term, this service should be updated to at least 6.x and ideally (AWS recommendation) to 7.x to get completely up to date. It might be easier to update all the way, all at once or it might be easier to update minimally until we reach a future EOL date.
The text was updated successfully, but these errors were encountered: