Skip to content
This repository was archived by the owner on Apr 7, 2026. It is now read-only.

fix: allow arbitrary env keys eg valueFrom#41

Open
lizthegrey wants to merge 3 commits intopyroscope-io:mainfrom
lizthegrey:patch-1
Open

fix: allow arbitrary env keys eg valueFrom#41
lizthegrey wants to merge 3 commits intopyroscope-io:mainfrom
lizthegrey:patch-1

Conversation

@lizthegrey
Copy link
Copy Markdown

No description provided.

@pyroscope-io pyroscope-io deleted a comment from CLAassistant Dec 24, 2021
@lizthegrey
Copy link
Copy Markdown
Author

Testing this against my own vendored copy, will report back...

@kolesnikovae
Copy link
Copy Markdown
Contributor

Thank you for the contribution @lizthegrey!

Yeah, I think we should keep the current behavior of env for backward compatibility. We can introduce an additional variable, although it will be difficult to combine them.

Alternatively, since the main scenario for this is using secrets, we could use the envFrom directive:

{{- if .Values.envFromSecret }}
envFrom:
- secretRef:
    name: {{ .Values.envFromSecret }}
{{- end }}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants