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 Spring Boot to 2.7.6 #47

Merged
merged 2 commits into from
Jan 10, 2023
Merged

Update Spring Boot to 2.7.6 #47

merged 2 commits into from
Jan 10, 2023

Conversation

pvannierop
Copy link
Contributor

Client pointed out a security issue with the current version of Spring. This PR will upgrade Spring Boot to 2.7.6 and use JRE 11.

@pvannierop pvannierop requested a review from inodb December 22, 2022 09:30
@pvannierop pvannierop self-assigned this Dec 22, 2022
Copy link
Member

@inodb inodb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me, I did make some minor changes to the docker base image to be in line with cBioPortal/cbioportal#9890 (hope that's ok)

We don't really have good testing set up for session service functionality in isolation (just running all the cbioportal e2e tests against it I guess)

Did y'all test this in any way @pvannierop or @oplantalech ?

@@ -0,0 +1 @@
spring.mvc.pathmatch.matching-strategy=ant-path-matcher
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pvannierop @oplantalech actually one comment about this. Is there a way we can pass this in another way. Reason I'm asking is that I would ideally prefer installers having to update their existing application.properties files

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@inodb
How this prop is passed to the application indeed is the responsibility of the installer. Or did not mean I would ideally prefer installers not having to update their existing application.properties files?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@inodb
If the latter, we can try an approach with multiple property sources like described here.

Copy link
Member

@inodb inodb Dec 30, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry yes I meant not having to update their existing files. Especially like in this case where it really shouldn't be a user customizable property

Spring often has ways of configuring this through either properties or having it hardcoded. I prefer the latter if possible. Multiple property files could work too otherwise by putting all "don't touch this" configurable spring stuff in one file

@pvannierop
Copy link
Contributor Author

pvannierop commented Dec 23, 2022 via email

@pvannierop pvannierop requested a review from inodb January 5, 2023 14:13
@inodb inodb merged commit 4a35236 into master Jan 10, 2023
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.

3 participants