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

Templating is broken #83

Open
sbaier1 opened this issue Nov 17, 2020 · 3 comments
Open

Templating is broken #83

sbaier1 opened this issue Nov 17, 2020 · 3 comments

Comments

@sbaier1
Copy link

sbaier1 commented Nov 17, 2020

Describe the bug:

The template patch field in the ExternalSecret CRD is not handled correctly in the controller. The internal datatype is wrong, making it impossible to use the field.

Setting a basic template leads to errors like this one:

Failed to watch *v1alpha1.ExternalSecret: failed to list *v1alpha1.ExternalSecret: v1alpha1.ExternalSecretList.Items: []v1alpha1.ExternalSecret: v1alpha1.ExternalSecret.Spec: v1alpha1.ExternalSecretSpec.Template: base64Codec: invalid input, error found in #10 byte of ...|template":{"type":"k|..., bigger context ...|n"}],"storeRef":{"name":"aws-secrets"},"template":{"type":"kubernetes.io/dockerconfigjson"}},"status|...

Expected behavior
Template should patch the resulting secret

Steps to reproduce the bug:
Set a template patch like the example above (JSON format: {"type":"kubernetes.io/dockerconfigjson"}})

Anything else we need to know?:
Filed a fix proposal PR #84

Environment details::

  • Kubernetes version (e.g. v1.18.9): v1.17.12-eks-7684af
  • Secret-Manager version (e.g. v0.2.0): current master branch
  • SecretStore type(e.g. Vault vs AWS SecretManager): AWS secretmanager
  • Install method (e.g. helm or static manifests): helm

/kind bug

@ahmedmus-1A
Copy link

Hello @sbaier1 , is there any updates in this issue ? i am stuck with the same problem

@sbaier1
Copy link
Author

sbaier1 commented Jan 12, 2021

hey, well you can build and use my fork if you urgently need to fix it. (That's what I'm currently doing).

I originally considered getting that linked PR merged, but after checking in with the the external secrets community (see the slack link on the external secrets org), it doesn't seem worth the effort, since this project + the other external secrets controllers are currently in the process of merging into a single, unified controller so it doesn't seem worth the effort to contribute to this project at the moment. If the problem persists in the resulting controller, i will probably propose the changes there instead.

@devth
Copy link
Contributor

devth commented Jan 12, 2021

Is itscontained/secret-manager officially merging into external-secrets/external-secrets? If so there should be a fat notice in this README.

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

Successfully merging a pull request may close this issue.

3 participants