-
Notifications
You must be signed in to change notification settings - Fork 554
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
Upgrade targeting-client #24833
Upgrade targeting-client #24833
Conversation
@@ -12,6 +12,7 @@ val common = library("common") | |||
awsCore, | |||
awsCloudwatch, | |||
awsDynamodb, | |||
awsKinesis, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NB: I think we'll also need to explicitly define the dependency for ec2 now as well. It's required here https://github.com/guardian/frontend/blob/main/admin/app/controllers/admin/TroubleshooterController.scala#L3, so we need to add val awsEc2 = "com.amazonaws" % "aws-java-sdk-ec2" % awsVersion
to Dependencies.scala
We were seeing a deprecation warning when directly instantiating the
The docs suggest alternative approaches to creating service clients, specifically using a client builder. However, the resulting type of the client builder is a different type to what we need (i.e. we get From the sdk we can see that, after creating and updating the client builder, we can call the |
guardian/frontend#24833 Scalactic version conflicts were causing compilation failures when compiling tests in frontend ``` java.lang.NoSuchMethodError: 'void org.scalactic.BooleanMacro.<init>(scala.reflect.macros.whitebox.Context, java.lang.String)' ```
We were seeing a failing build in team city, eg https://teamcity.gutools.co.uk/viewLog.html?buildId=756934&buildTypeId=dotcom_master&tab=buildLog, due to an error during test compilation. The error was a result of incompatible versions of scalactic. A version of scalactic was being defined in targeting-client, however that dependency did not need to be defined (it wasn't being directly used anywhere in the project). Scalactic was removed from targeting-client and a new version of the library was published (1.1.2 - note that the deploy of 1.1.1 failed because I didn't have a valid setup, so we moved straight to publishing 1.1.2 in case there was a conflict from the partly-failed publishing of 1.1.1). Hopefully now we have a working build - we may still want to look at removing the deprecated function. |
Hi @DavidLawes ! I notice that the build didn't quite pass, but if you rebase on top of main to get #24845, then this error will go away:
|
c971573
to
797777d
Compare
@@ -30,6 +31,7 @@ class SafeBlockingKinesisAppender(logbackOperations: LogbackOperationsPool) exte | |||
resetTimeout = 10.seconds, | |||
)(logbackOperations.logbackOperations) | |||
|
|||
@nowarn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR changes aws-java-sdk-kinesis
from 1.11.26
to 1.11.240
. In this version AmazonKinesisAsyncClient
is deprecated. A separate ticket has been created to refactor KinesisAdapter.scala
and get rid of the deprecated class and the @nowarn
annotation: #24846
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 Looks good to me!
Seen on PROD (merged by @ioannakok 14 minutes and 52 seconds ago)
|
What does this change?
In advance of updating the Scala version we want to update as many dependencies as possible to be compatible with both 2.12 and 2.13.
This change bumps targeting-client to the latest version which is compatible with both 2.12 and 2.13.
As part of this PR
aws-java-sdk-kinesis
andaws-java-sdk-ec2
had also to change from1.11.26
to1.11.240
.Does this change need to be reproduced in dotcom-rendering ?
Screenshots
What is the value of this and can you measure success?
Checklist
Does this affect other platforms?
Does this affect GLabs Paid Content Pages? Should it have support for Paid Content?
Does this change break ad-free?
Does this change update the version of CAPI we're using?
Accessibility test checklist
Tested