Update Facia & CAPI clients (and ETag-caching library) #27705
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 ofetag-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