- 13 Jul, 2021 1 commit
-
-
Thomas Beermann authored
-
- 02 Jul, 2021 1 commit
-
-
Thomas Beermann authored
-
- 29 Jun, 2021 1 commit
-
-
femiadeyemi authored
-
- 23 Jun, 2021 1 commit
-
-
Thomas Beermann authored
-
- 21 Jun, 2021 1 commit
-
-
femiadeyemi authored
Modification: - introduce an anotation called ForeignKey. This can be use to ensure that the uuid reference in another entity is valid and cascading effect are maintained. - modify some entities and added some new entities like Image, Person and Software. Also, corresponding repositories and services. - redesign the base service and create a kind of base repository Target: master
-
- 26 May, 2021 1 commit
-
-
femiadeyemi authored
Motivation: We need to store media data for some of the entities and neo4j is not design to store images, video, etc.. Hence, to avoid using multiple dbs, we sort for a solution that can store the metadata and the media data. Modification: - remove neo4j dependency and add mongo - change the entities details and re-design it to suit the new db - adjust the api design - delete all neo4j relationship pojos - adjust the tests according to the new definitions Result: Cerebrum now uses mongo db. Target: master
-
- 19 May, 2021 3 commits
-
-
femiadeyemi authored
-
femiadeyemi authored
Motivation: Meeting up with the new API design requires that the market-user and organisation entity are realign. Modification: - factor out some part of market-user and create a new class (person) - make organisation enity to extend audit-metadata and some properties were added. - use the lombok project to reduce the boilerplate code in both the market-user and organisation entities. - add 'person' to the list of PrefixEnum in the CerebrumEntityUuidGenerator Result: Market-user and Organisation entity are now re-worked Target: master
-
femiadeyemi authored
Motivation: Some reported vulnerabilities of the dependencies by OWASP make the pipeline broken. Modification: - upgrade spring boot starter parent version from 2.3.5.RELEASE to 2.3.10.RELEASE - upgrade hibernate-validator from 6.0.19.Final to 6.2.0.Final - updgrade neo4j-java-driver-spring-boot-starter from 4.1.1.0 to 4.2.4.0 - update list of OWASP check and supress some false positive alarms Result: Build pipeline succeeds. Target: master
-
- 18 May, 2021 1 commit
-
-
femiadeyemi authored
Motivation: To gain insight on cerebrum-app, the spring framework provide the facility to expose the application metrics to monitoring service like Prometheus on Kubernetes. Modification: - enable graceful shutdown - add spring boot actuator and prometheus registry micrometer dependencies - expose the actuator endpoint that will provides: health, info, metric etc. - avoid 404 error on request to /favicon.ico Result: Cerebrum now makes it metrics available and can be shutdown gracefully. Target: master
-
- 17 May, 2021 1 commit
-
-
femiadeyemi authored
Motivation: To fullfill the service metadata description defined by the cloud management board, new properties need to be added to the market-service entity. Modification: - add lombok dependency to the cerebrum project to avoid some boilterplate codes - add some few new properties to the market-service entity - enable database auditing to keep track of when an entity was created and when it was last modified. - adjust the MarketServiceRepository to fit the new market-service properties definition Result: Market-service entity contain some new properties and some few name change. Target: master
-
- 15 Mar, 2021 1 commit
-
-
femiadeyemi authored
-
- 21 Feb, 2021 2 commits
-
-
femiadeyemi authored
-
femiadeyemi authored
-
- 20 Feb, 2021 3 commits
-
-
femiadeyemi authored
-
femiadeyemi authored
-
femiadeyemi authored
-
- 03 Dec, 2020 2 commits
-
-
femiadeyemi authored
Motivation: Automated ci/cd is desirable process we will like to adhere to in our pipeline. Since we already have a local kubernetes cluster running on the production machine, we need to ensure that when a new tag is release, the cluster is notified. Modification: - add a new pipeline stage called `docker`. This will be use for the building and deploy the image into the docker hub. - deploy stage will now be responsible for trigger automated update of the image in the cluster. Result: Getting closer to fully automated ci/cd Target: master
-
femiadeyemi authored
-
- 02 Dec, 2020 7 commits
-
-
femiadeyemi authored
-
femiadeyemi authored
-
femiadeyemi authored
Result: avoid `pseudo-terminal will not be allocated because stdin is not a terminal` error.
-
femiadeyemi authored
-
femiadeyemi authored
-
femiadeyemi authored
-
femiadeyemi authored
Motivation: Since we are moving to dockerize deployment, some variables, like the neo4j hostname needs to be set different base on the environment set up. Also, we need to seperated the images that will be generated when a normal commit is made and when a release is trigger. Modification: - expose the neo4j host name as configurable variable - seperate docker image generated from a commit and a tag release - add production_deployment to ci/cd deploy stage. This will be use to depoly to the production system. However, it just include a test to see if the ssh will work. Result: Two different docker images will be build, one for stable tagged release and the other for development. These images will be push to different docker repositories. Target: master
-
- 10 Nov, 2020 4 commits
-
-
femiadeyemi authored
-
femiadeyemi authored
Motivation: A new uuid is generated for an entity that will be save on the db.. This is use as a primary way of uniquely identify a particular node. To ensure the uniqueness of the uuid, two factor were considered which are: - uuid version 1 - secure random number However the secured random number is currently generated causing the thread to block in a VM (for details explaination see https://tersesystems.com/blog/2015/12/17/the-right-way-to-use-securerandom/). Hence the behaviour of the system become unpredicate and most likely will fail if the request will required the uuid to be generated. Modification: - change how the secured random number is generated - minor typo fix inside the MarketUserRepository Result: The generation of cerebrum custom uuid now work seemly on both local machine and VMs. Hence, all requests are now process as expected. Target: master
-
femiadeyemi authored
-
femiadeyemi authored
Motivation: Keep cerebrum up-to-date. Modification: - change the spring-boot version to 2.3.5 - upgrade the springdoc-openapi-ui to version 1.4.8 to avoid the classpath problem - use the latest spring boot version of the neo4j driver - unity aai jwt header token is at+jwt however, the latest springframework security does not support this. Hence. exclude the current version of nimbus-jose-jwt and add version 7.9 that support at+jwt header. - inside the application.yml and application-dev.yml use the properties setting for the neo4j instead of the spring neo4j properties - enable more neo4j logs info - use the proper variable name for the sceret value inside the docker file. Result: No visible changes to the end user
-
- 16 Oct, 2020 4 commits
-
-
femiadeyemi authored
-
femiadeyemi authored
change to debug mode
-
femiadeyemi authored
-
femiadeyemi authored
-
- 15 Oct, 2020 6 commits
-
-
femiadeyemi authored
`tar` -> `jar`
-
femiadeyemi authored
-
femiadeyemi authored
Motivation: When the test stage of the ci/cd is trigger, it currently fail. The main reason is that it took more than the stipulated time of one hour to run. Modification: skip unit/integration tests Result: no testing
-
femiadeyemi authored
Motivation: Maven test are unncessarily ran at least twice and some stage that were declared that were not use. This cause some unexpected behaviour in the ci/cd build. Also, the ci/cd fail because of some false postive in the dependency vulnerabilities scan Modification: - Define only neccessary stages and use them accordingly. - add some few dependecies supression Result: - Keep the ci/cd simple and avoid running multiple tests - when `mvn org.owasp:dependency-check-maven:check` is run Vulnerabilities found equal 0 Target: master Review: https://gitlab.hzdr.de/hifis-technical-platform/helmholtz-cerebrum/-/merge_requests/39
-
femiadeyemi authored
Motivation: All authenticated user should be store into cerebrum data-storage (neo4j). At the momement this is not the case. Modification: - ensure that when the autheticated user hit /api/v0/users/whoami and the user is unknown to cerebrum, a new user will be created. - add findByEmailAndSub method in the user repository to search the database if user with the supplied email and sub exist - add a createEnity method inside CerebrumService interface that are implemented inside CerebrumServiceBase abstract class. This will be use when the uri location is not needed. Result: Unkown user that have been authenticated will be store by cerebrum. Target: master Review: https://gitlab.hzdr.de/hifis-technical-platform/helmholtz-cerebrum/-/merge_requests/38
-
femiadeyemi authored
-