Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a secret generation function to setup object storage #146

Open
blancharda opened this issue Jun 11, 2024 · 1 comment
Open

Implement a secret generation function to setup object storage #146

blancharda opened this issue Jun 11, 2024 · 1 comment
Assignees
Labels
enhancement ✨ New feature or request

Comments

@blancharda
Copy link
Member

blancharda commented Jun 11, 2024

Is your feature request related to a problem? Please describe.

As Ezra I want a way to manually setup the S3 configuration directly with the config chart so that I do not need to manage a package out of band in a bundle for this.

Describe the solution you'd like

  • Given I have the following for an S3 connection:
    • ENDPOINT
    • ACCESS_KEY
    • ACCESS_KEY_SECRET
    • BUCKET_PREFIX
    • BUCKET_SUFFIX
  • When I provide these under the appropriate key (objectStorage.s3) to the config chart
  • Then the config chart generates the appropriate gitlab-object-store secret for this service with the appropriate format for an S3 API compliant object storage provider

Describe alternatives you've considered

We could keep the status quo and change Mattermost to not have this pattern but this pattern is a nice to have when you need to manually provide a username / password.

Additional context

@blancharda blancharda added the enhancement ✨ New feature or request label Jun 11, 2024
@Racer159
Copy link
Contributor

Note this should also be documented in the common SWF docs and each depending app's configuration.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants