Describe the bug
When one wants to use minio as an object storage and shared object at the same time, an error occur.
A minio module is created and a second one named minio_s3_fs is attempted to be created. This fails because the secrets created for the minio module have the same name with the one for minio_s3_fs.
To Reproduce
Steps to reproduce the behavior:
- In the Onprem deployment, go to 'parameters.tfvars'
- Uncomment
minio = {} and minio_s3_fs = {}
- Deploy Armonik
- See error
Expected behavior
The deployment should succeed
Screenshots

Infra
- Target (Local, AWS, Docker compose, etc..) : Onpremise
- ObjectStorage: minio
Describe the bug
When one wants to use minio as an object storage and shared object at the same time, an error occur.
A
miniomodule is created and a second one namedminio_s3_fsis attempted to be created. This fails because the secrets created for theminiomodule have the same name with the one forminio_s3_fs.To Reproduce
Steps to reproduce the behavior:
minio = {}andminio_s3_fs = {}Expected behavior
The deployment should succeed
Screenshots
Infra