If you are using Mia-Platform PaaS you don't have to do anything, the Console will automatically update. For on-premise Console installations, please contact your Mia-Platform referent to know how to use the Helm chart version indicated in the release note of the version you want to update.
Verify it checking out the dedicated page.
Check out this page to know how to update your CMS
No, at the moment you can't. The entire configuration of the project will be released.
Anyway, before deploy, when you have to choose the environment, the Console will show you a comparison between the services you want to release and those that are currently running in that environment.
Check out the related section for details.
The Deploy of a project will only release the configuration set as a Git repo path during project creation.
From Console, click on Git provider icon, at the top right part of the Console, to open the project configurations repository
If you don't find what you're looking for, you can read all documentation about Deploy in the dedicated section
We do not recommend this debugging practice, instead, you should always write good tests for your microservices. You can also run the microservice locally.
Furthermore, logs can help you to understand what your microservice is doing. The use of logging level allows you to distinguish debug messages that you want to have only in no production environments from those that are useful to monitor the applicative state (errors, warnings, etc).
Consider that the Console allows you to quickly deploy your microservices in a dedicated environment, so you can try online immediately.
Example of test
Yes, you can create a microservice from a Docker Image. The only requirement is that the Docker Image needs to be already built and available on a registry.
No, it's not mandatory. Naturally, starting from a Mia-Platform Template or using Mia-Platform Service Libraries has many advantages and allows your microservice to be compliant with all best practices(such as testing, logging, health routes, etc).
In order to do this, you can read the Mia-Platform headers. These headers provide information about:
- Id, group and selected properties of the eventual logged in user
- The eventual identified client that made the request
- The eventual origin from the Back-Office.
Microservices templates, using Mia-Platform Service Libraries, let you to easily access to these request headers.
No, you can only use HTTP.
You can change the state (PUBLIC, DRAFT, TRASH or DELETED) of a document by making a POST request. Check out the CRUD Service documentation for details.
You can visit the Documentation Portal to see the documentation of your CRUDs APIs.
You can change the visibility of any endpoint (and its routes) in the endpoint Management section by disabling the
Show in API Portal flag. Check out the related section for more details.
You can also use the Mia-Platform Service Libraries that help you to get a proxy towards the API Gateway.
Checkout the Mia service Node.js Library documentation to know how to call the platform services with a proxy object