You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#@ for file in app.mountFiles:
- mountPath: #@ file.mountPath
name: #@ file.name.split('.')[0]
subPath: #@ file.name
#@ end
I can then mount files to the various application deployments with variable content as needed. Obviously, this isn't possible, as it is not possible to use data values within a data values file.
If I were to use a function, then this gets messy, quickly, as I then have to put the file content in a lib/function, and then I have to put the mountPath somewhere seperate.
prembhaskal
added
discussion
This issue is not a bug or feature and a conversation is needed to find an appropriate resolution
and removed
carvel triage
This issue has not yet been triaged for relevance
labels
Dec 5, 2023
I know there is a work around for this, however I don't think it fits my particular use case very nicely, and wondering if there's a better solution.
So consider my schema:
Then in a deployment template:
I can then mount files to the various application deployments with variable content as needed. Obviously, this isn't possible, as it is not possible to use data values within a data values file.
If I were to use a function, then this gets messy, quickly, as I then have to put the file content in a
lib/function
, and then I have to put themountPath
somewhere seperate.For example, I then will have a lib:
And my deployment becomes:
Clearly this is not nice at all, and inflexible. How is it recommended to handle this situation?
Thanks
The text was updated successfully, but these errors were encountered: