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

being able to use kubesec with "non secret" files in YAML stream file #30

Open
davinkevin opened this issue Aug 23, 2019 · 0 comments
Open

Comments

@davinkevin
Copy link

Hi,

It could be simpler to use to be able to run kubesec commands on multi "stream" yaml, even if doesn't contain only secrets.

For example, the file all.yaml:

apiVersion: v1
data:
  application.yaml: |2

    podcastserver:
      rootfolder: /podcasts
      concurrent-download: 40
      max-update-parallels: 256
      number-of-day-to-download: 30
      number-of-day-to-save-cover: 30

    spring:
      datasource.url: jdbc:h2:tcp://database:1521/podcast-server
      jpa.hibernate.ddl-auto: none
kind: ConfigMap
metadata:
  name: podcast-server-d989t5tgb4
  namespace: podcast-server
---
apiVersion: v1
data:
  api.youtube: ofajoeaijeoijeaoaeijeofiajaef
kind: Secret
metadata:
  name: podcast-server-b5cddm29mt
  namespace: podcast-server
type: Opaque

I would like to be able to run something like this :

$ cat all.yaml | kubesec -d - | kubectl apply -f -

But, right now, I have the following result:

image

@davinkevin davinkevin changed the title being able to use kubesec with "non secret" files being able to use kubesec with "non secret" files in YAML stream file Aug 23, 2019
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

No branches or pull requests

1 participant