Introduction
In this release, we have created a new system for creating microservice templates based on Git projects, which will allow the creation of platform microservices from those templates, being able to build the same microservice in different environments.
In this way, several models have been incorporated, and the archetypes we had before have been transferred, in order to improve their maintenance. The templates that we have by default are the following ones:
Template with native Spring Boot 3 with GraalVM. Support for the deployment of native Microservices with GraalVM
Template with Spring Boot 3 with Docker.
Template with the archetype of the ML Model.
Template with the archetype of the IOT Client.
Template with the archetype of Notebooks.
How?
From the Development -> Microservice Templates menu, you can create templates in Java8, Java17 and Java17 with GraalVM, specifying the url of the Git where you have created the microservice, and being able to publish it from the Platform, creating a microservice from this template.
When creating a template, it is necessary to indicate the path where the pom.xml of the microservice is located in Git, and the Dockerfile, except if you have indicated that GraalVM is used with Java17, since in this case the Dockerfile is not needed for creating the image.
Templates cannot be created with other languages,. However, we have preloaded some templates that are identical to the options we had before, when creating a microservice. This allows for a better maintenance of these as they are externalized in Git. For example, we can change the version of Spring Boot in the Git repository and bring those changes.
In this way, you will be able to see a template for each of the archetypes. These templates will not be editable. The following image shows the template for the ML Model archetype:
Another one for the IOT client archetype:
And another for the Notebooks archetype:
When you are going to create a microservice from the Development -> Microservice Management menu, the created and preloaded templates will appear as an option to choose from the drop-down.
In this way, you can have the template created in a repository and decide whether to clone it in a different Git, indicating the URL, user and token as always, and selecting the Jenkins and CaaS configuration, thus allowing you to deploy the same templated microservice in different environments.