Skip to content
This repository was archived by the owner on Nov 23, 2024. It is now read-only.
This repository was archived by the owner on Nov 23, 2024. It is now read-only.

"Not encrypted" line causing trouble in Spinnaker pipeline #144

@gjgarryuan

Description

@gjgarryuan

https://github.com/futuresimple/helm-secrets/blob/5f91bdfc66bd901e3088aac2efa2d107a055ea39/secrets.sh#L303

I am using helm secrets template command to render the helm chart and upload to S3 for later Spinnaker pipeline deployment uses.

However, if the command is used with a template secrets file not encrypted (due to no secrets at all but just serve as a place holder), the resulting yaml file will always contain the Not encrypted: as the first line, which the Spinnaker pipeline doesn't like and fail the pipeline with this error:

Exception ( Deploy Manifest )
Missing required field 'kind' on manifest: {Not encrypted=helm/deployments/some-tenant/staging/secrets.yaml}

It will be very convenient if the plugin can expose an option which tells the secret plugin to not generate that Not encrypted: line, or make that line into a comment.

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