Skip to content

minio as object storage and shared storage at the same time #1305

Description

@jdongo-aneo

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:

  1. In the Onprem deployment, go to 'parameters.tfvars'
  2. Uncomment minio = {} and minio_s3_fs = {}
  3. Deploy Armonik
  4. See error

Expected behavior
The deployment should succeed

Screenshots

image

Infra

  • Target (Local, AWS, Docker compose, etc..) : Onpremise
  • ObjectStorage: minio

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions