Skip to content

Add support for additionalCommandArgs and configuratable S3 secret keys. #653

@austinmarten1

Description

@austinmarten1

Problem

The current chart limits barmanObjectStore configuration:

  • No support for additionalCommandArgs

  • S3 secret keys are fixed (ACCESS_KEY_ID, ACCESS_SECRET_KEY)

Currently:

Only accepts fixed S3 secret key names and no way to add extra barman command arguments Like you can within the raw manifests.

Desired Behavior

Allow custom S3 secret key names (e.g. aws-access-key-id, aws-secret-access-key)

Add additionalCommandArgs support

This will allow the ability to Use existing S3 secrets without renaming keys and pass custom barman options into additionalCommandArgs.

Files to Update

  • values.yaml
  • templates/_barman_object_store.tpl
  • templates/_backup.tpl

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions