Skip to content

Release 10.1.2 broke S3 existingSecret support #223

@DaDummy

Description

@DaDummy

After upgrading to 10.1.2 an existing secret is no longer correctly recognized, which in turn causes the seeder to fail with the following error:

rake aborted!
ArgumentError: Missing required arguments: aws_access_key_id, aws_secret_access_key (ArgumentError)

          raise ArgumentError, "Missing required arguments: #{missing.join(', ')}"

The issue appears to be, that the secretKeys configured in values.yaml are no longer correctly applied to the resulting seeder job's definition.

Instead of

        envFrom:
[...]
        - secretRef:
            name: (existing secret)

the following definition is expected here:

        env:
        - name: (target environment var name)
          valueFrom:
            secretKeyRef:
              key: (existing secret key)
              name: (existing secret)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions