Skip to content

Commit cbd05ac

Browse files
JGiolaJGiola
authored
Add empty dir docs (#2215)
* docs: add empty dir docs * fix: typos * fix: move rn section under the correct spot
1 parent aec8ad7 commit cbd05ac

File tree

3 files changed

+111
-89
lines changed

3 files changed

+111
-89
lines changed

‎docs/development_suite/api-console/api-design/img/empty-dir.png‎

27.2 KB
Loading

‎docs/development_suite/api-console/api-design/services.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -531,6 +531,24 @@ You need to give **additional permissions** to the console service account in or
531531
532532
It is also possible to use Kubernetes secrets to setup specific environment variables, follow this [link](/development_suite/api-console/api-design/services.md#environment-variable-configuration) to understand how to do so.
533533
534+
#### Empty dirs
535+
536+
You can use this section to define special mounting points in your services.
537+
This mountpoints can be used to create an actual empty directory on the generated Kubernetes pod. This can be useful if
538+
the service run with low privileges and cannot change anything in its default file system because the generated folder
539+
will be readwritable by the process.
540+
Another common use case is to allow sharing data between the different containers of the service, because if you use
541+
the same empty dir in one or more container of the same service. This can be useful if one of the container can generate
542+
files that must be consumed by another container.
543+
544+
![Empty dir](img/empty-dir.png)
545+
546+
You can create two different types of empty dirs, the first one will use space on the disks of the kubernetes node where
547+
the workload will run or using the part of the dedicated memory to the service saving the data directly in the RAM.
548+
549+
The main difference is that using the RAM is faster and the data will be lost after a pod restart, using the file system
550+
will preserve the data between pod crashes but the speed of the read writes are tied to the medium used by the node disk.
551+
534552
### Provide a CA Certificate to a custom service
535553
536554
In an enterprise environment, to encrypt SSL connections, there could be a set of custom certificates signed by one or more trusted certificates.

‎docs/release-notes/v14.0.1.md‎

Lines changed: 93 additions & 89 deletions
Original file line numberDiff line numberDiff line change
@@ -1,89 +1,93 @@
1-
---
2-
id: v14.0.1
3-
title: Version 14.0.1 Release Notes
4-
sidebar_label: v14.0.1
5-
image: "img/release-note-link-preview.png"
6-
---
7-
8-
_June 26th, 2025_
9-
10-
## Simplified Promotion flow
11-
12-
In a Environment Based Project, you can now decide to promote an environment with the Simplified mode, in order to speed up your flow.
13-
When this mode is selected, once the Public variables have been chosen, the changes of the chosen Environment will be directly applied in the target Environment.
14-
15-
<div style={{width: '400px', maxWidth: '100%', display: 'flex', alignItems: 'center', borderRadius: '4px', overflow: 'hidden'}}>
16-
17-
![Promotion](img/promotion.png)
18-
19-
</div>
20-
21-
To discover more about Environment Configuration Promotion and the Simplified mode, head to the related [documentation page](/development_suite/set-up-infrastructure/env-based-management.md#simplified-mode).
22-
23-
## Console
24-
25-
### Improvements
26-
27-
#### Migration to Env Based available on Project's Advanced tab
28-
29-
From now on, you can start the migration flow to the new Env Based workflow directly form the Advanced tab available in the Project's Settings section.
30-
31-
#### Model used by Mia-Assistant is visible in the chatbot
32-
33-
From now on, information about the model used by Mia-Assistant is visible to users interacting with the chatbot.
34-
35-
#### Secrets support in Flow Manager Configurator
36-
37-
Starting from version `2.7.0` of the Flow Manager service, it is now possible to instruct the service to use **secrets** in specific parts of the configuration provided via the Configurator.
38-
39-
For details on how to use this feature, please refer to the [official documentation](/development_suite/api-console/api-design/flow-manager-configurator/overview.md#secrets).
40-
41-
### Bug Fix
42-
43-
This version address the following bug:
44-
45-
* it has been fixed a bug that was showing a blank page when entering the Console for the first time
46-
47-
## Microfrontend Composer
48-
49-
### Back-Lit Library
50-
51-
The new version `v1.5.18` of the back-kit library is available!
52-
53-
Refer to back-kit [changelog](/microfrontend-composer/back-kit/changelog.md) for finer-grained details of new versions.
54-
55-
#### Improvements
56-
57-
##### Support for Title and Content Interpolation in `bk-notifications`
58-
59-
Added possibility to interpolate title and content of the `bk-notifications` component
60-
61-
#### Bug Fix
62-
63-
- Fixed `bk-table` wrong column widths introduced with the new Chrome/Chromium version
64-
65-
## Marketplace
66-
67-
### Marketplace Updates
68-
69-
#### Flow Manager Service 2.7.0
70-
71-
The new version `2.7.0` of the Flow Manager Service is available!
72-
73-
The Flow Manager supports the resolution of Kubernetes secrets for a set of configuration properties.
74-
75-
Please refer to the [official documentation](/runtime_suite/flow-manager-service/30_configuration.md#secrets-resolution) for more details.
76-
77-
##### Fixed
78-
79-
Errors that occur during the deep merge hook execution are now properly logged by the service.
80-
81-
#### FHIR Adapter 1.2.0
82-
83-
The new version `1.2.0` of the FHIR Adapter is available!
84-
85-
This version adds support for bundle transactions, that can be triggered by a request to the new `POST /transaction/:transactionId` endpoint.
86-
87-
## How to update your Console
88-
89-
For self-hosted installations, please head to the [self hosted upgrade guide](/infrastructure/self-hosted/installation-chart/100_how-to-upgrade.md) or contact your Mia-Platform referent and upgrade to _Console Helm Chart_ `v14.2.2`.
1+
---
2+
id: v14.0.1
3+
title: Version 14.0.1 Release Notes
4+
sidebar_label: v14.0.1
5+
image: "img/release-note-link-preview.png"
6+
---
7+
8+
_June 26th, 2025_
9+
10+
## Simplified Promotion flow
11+
12+
In a Environment Based Project, you can now decide to promote an environment with the Simplified mode, in order to speed up your flow.
13+
When this mode is selected, once the Public variables have been chosen, the changes of the chosen Environment will be directly applied in the target Environment.
14+
15+
<div style={{width: '400px', maxWidth: '100%', display: 'flex', alignItems: 'center', borderRadius: '4px', overflow: 'hidden'}}>
16+
17+
![Promotion](img/promotion.png)
18+
19+
</div>
20+
21+
To discover more about Environment Configuration Promotion and the Simplified mode, head to the related [documentation page](/development_suite/set-up-infrastructure/env-based-management.md#simplified-mode).
22+
23+
## Console
24+
25+
### Improvements
26+
27+
#### Migration to Env Based available on Project's Advanced tab
28+
29+
From now on, you can start the migration flow to the new Env Based workflow directly form the Advanced tab available in the Project's Settings section.
30+
31+
#### Model used by Mia-Assistant is visible in the chatbot
32+
33+
From now on, information about the model used by Mia-Assistant is visible to users interacting with the chatbot.
34+
35+
#### Secrets support in Flow Manager Configurator
36+
37+
Starting from version `2.7.0` of the Flow Manager service, it is now possible to instruct the service to use **secrets** in specific parts of the configuration provided via the Configurator.
38+
39+
For details on how to use this feature, please refer to the [official documentation](/development_suite/api-console/api-design/flow-manager-configurator/overview.md#secrets).
40+
41+
#### Support for Empty Dir volumes
42+
43+
Added support to specify an empty dir mount point for a service and/or its additional containers
44+
45+
### Bug Fix
46+
47+
This version address the following bug:
48+
49+
* it has been fixed a bug that was showing a blank page when entering the Console for the first time
50+
51+
## Microfrontend Composer
52+
53+
### Back-Lit Library
54+
55+
The new version `v1.5.18` of the back-kit library is available!
56+
57+
Refer to back-kit [changelog](/microfrontend-composer/back-kit/changelog.md) for finer-grained details of new versions.
58+
59+
#### Improvements
60+
61+
##### Support for Title and Content Interpolation in `bk-notifications`
62+
63+
Added possibility to interpolate title and content of the `bk-notifications` component
64+
65+
#### Bug Fix
66+
67+
- Fixed `bk-table` wrong column widths introduced with the new Chrome/Chromium version
68+
69+
## Marketplace
70+
71+
### Marketplace Updates
72+
73+
#### Flow Manager Service 2.7.0
74+
75+
The new version `2.7.0` of the Flow Manager Service is available!
76+
77+
The Flow Manager supports the resolution of Kubernetes secrets for a set of configuration properties.
78+
79+
Please refer to the [official documentation](/runtime_suite/flow-manager-service/30_configuration.md#secrets-resolution) for more details.
80+
81+
##### Fixed
82+
83+
Errors that occur during the deep merge hook execution are now properly logged by the service.
84+
85+
#### FHIR Adapter 1.2.0
86+
87+
The new version `1.2.0` of the FHIR Adapter is available!
88+
89+
This version adds support for bundle transactions, that can be triggered by a request to the new `POST /transaction/:transactionId` endpoint.
90+
91+
## How to update your Console
92+
93+
For self-hosted installations, please head to the [self hosted upgrade guide](/infrastructure/self-hosted/installation-chart/100_how-to-upgrade.md) or contact your Mia-Platform referent and upgrade to _Console Helm Chart_ `v14.2.2`.

0 commit comments

Comments
 (0)