Skip to content
This repository has been archived by the owner on Jun 2, 2022. It is now read-only.

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

Open
gjgarryuan opened this issue Dec 17, 2019 · 0 comments
Open

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

gjgarryuan opened this issue Dec 17, 2019 · 0 comments

Comments

@gjgarryuan
Copy link

gjgarryuan commented Dec 17, 2019

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant