Open johnzheng1975 opened 1 month ago
This issue is currently awaiting triage.
SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
Then I want to try another solution like:
$ cat kustomization.yaml
generatorOptions:
disableNameSuffixHash: true
configMapGenerator:
- name: try01
files:
- application.yaml
- name: client
literals:
- securityChampion=$(yq e '.security.champion' ../asset-manifest.yaml)
I wish it can come out correct value, like
$ yq e '.security.champion' ../asset-manifest.yaml
aaa.bbb@ccc.com
However, it still show variable as below, not show aaa.bbb@ccc.com
$ kustomize build .
apiVersion: v1
data:
securityChampion: $(yq e '.security.champion' ../asset-manifest.yaml)
kind: ConfigMap
metadata:
name: client
Eschewed features
What would you like to have added?
Why is this needed?
can we use the files in parent folder, or any workarround for this? thanks.
Can you accomplish the motivating task without this feature, and if so, how?
we have to move all files in same folder of kustomization.yaml However, in real case, this is not true.
What other solutions have you considered?
copy duplicate files in kustomization.yaml, the code structure is ugly.
Anything else we should know?
No response
Feature ownership