-
Notifications
You must be signed in to change notification settings - Fork 1
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
#280: agent and server compatibility for Additional Data PATCH operation #283
Conversation
JaCoCo model module code coverage report - scala 2.13.11
|
JaCoCo agent module code coverage report - scala 2.13.11
|
JaCoCo reader module code coverage report - scala 2.13.11
|
JaCoCo server module code coverage report - scala 2.13.11
|
…ort PATCH; also updating config in our agent tests, also moving envelope related DTOs to model/ package
Release Notes:
|
…e and thus HTTP Dispatcher
…rs are not needed to be tested
… not needed to be tested
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.
Reviewed on a pair session
…nused endpoint and DTOs/aliases
…gent-to-server-in-v0-3-0 # Conflicts: # server/src/main/scala/za/co/absa/atum/server/api/controller/BaseController.scala # server/src/main/scala/za/co/absa/atum/server/api/controller/FlowController.scala # server/src/main/scala/za/co/absa/atum/server/api/controller/FlowControllerImpl.scala # server/src/main/scala/za/co/absa/atum/server/api/repository/PartitioningRepository.scala # server/src/test/scala/za/co/absa/atum/server/api/controller/FlowControllerUnitTests.scala
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.
LGTM
@@ -88,19 +88,21 @@ class GetPartitioningAdditionalDataIntegrationTests extends DBTestSuite{ | |||
) | |||
|
|||
function(fncGetPartitioningAdditionalData) | |||
.setParam("i_partitioning", partitioning1) | |||
.setParam("i_partitioning_id", fkPartitioning1) |
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.
You know, that you don't have to name the params, you can put them there positionally? Especially in one param functions, it's easier
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.
Yep, I know, but I find it nicer - more readable if it's named, especially if there are more functions; but for 1-2 params I think you are right, can be ommited
.execute { queryResult => | ||
val results = queryResult.next() | ||
assert(results.getInt("status").contains(11)) | ||
assert(results.getString("status_text").contains("OK")) | ||
assert(results.getString("ad_name").contains("ad_1")) | ||
assert(results.getString("ad_value").contains("This is the additional data for Joseph")) | ||
assert(results.getString("ad_author").contains("Joseph")) |
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.
Really need to switch to Balta 0.3, so much tidier 😉
Note: Additional Data = AD
What was done:
HttpURLConnectionBackend
->OkHttpSyncBackend
- inspired by java.net.ProtocolException: Invalid HTTP method: PATCH softwaremill/sttp#316 and Get scopes integration tests working raster-foundry/raster-foundry#5306 becauseHttpURLConnectionBackend
didn't support PATCH HTTP Method and we need it for AD update endpointpatchPartitioningAdditionalDataEndpointV2
andgetPartitioningEndpointV2
Note: If you want to run
AgentWithServerIntegrationTests
then:src/test/resources/reference.conf
accordingly - this is needed:atum.dispatcher.http.url="http://localhost:8080"
andatum.dispatcher.type="http"
Closes #280
Release notes: