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

Update Facia & CAPI clients (and ETag-caching library) #27705

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rtyley
Copy link
Member

@rtyley rtyley commented Jan 9, 2025

What is the value of this and can you measure success?

With guardian/facia-scala-client#287, the Facia client has been updated so that it can take advantage of ETag-caching, using the guardian/etag-caching library already used in Frontend since August 2023 with #26338.

What does this change?

As some changes were necessary to the etag-caching library to facilitate this, we need to update the version of etag-caching used by Frontend to v7.0.0. We also need to use an updated version of CAPI, as the CAPI version used by Facia was recently updated with guardian/facia-scala-client#341.

Although this change upgrades to the latest version of the Facia client, it doesn't turn on the new ETag-caching support there - that can come in a later PR, as it does involve switching to AWS SDK v2 (not everywhere in Frontend, just for where we use the Facia client, but that's still a significant change as the AWS STS credential creation has got more elaborate with AWS SDK v2).

Checklist

With guardian/facia-scala-client#287, the Facia client has
been updated so that it can take advantage of ETag-caching, using the
https://github.com/guardian/etag-caching library already used in Frontend since
August 2023 with #26338.

As some changes were necessary to the `etag-caching` library to facilitate
this, we need to update the version of `etag-caching` used by Frontend to v7.0.0.
We also need to use an updated version of CAPI, as the CAPI version used by Facia
was recently updated with guardian/facia-scala-client#341.

Although this change upgrades to the latest version of the Facia client, it doesn't
take advantage of the new ETag-caching support there - that can come in a later PR,
as it does involve switching to AWS SDK v2 (not everywhere in Frontend, just for
where we use the Facia client, but it's still a significant change as the AWS STS
credential creation has got more elaborate with AWS SDK v2).
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

Successfully merging this pull request may close these issues.

1 participant