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
But when I have multiple workloads or containers, this is a bit painful.
A post-processing yq command may be able to help too, but same approach, not user friendly.
Do we have an opportunity to introduce a new provisioner type (or something else) in order to patch a workload or a service directly in score-compose generate?
The text was updated successfully, but these errors were encountered:
@mathieu-benoit what kind of expression language do you suggest? how complex should it be?
Tools like jq and yq are very good at what they do, so we will never do something of equivalent complexity, but there is room for something simple potentially using the existing Go template language?
We wouldn't use a provisioner or workload resource like humanitec does, because it breaks the Score resource contracts but we could do something specific to score compose here?
I have this use case where I want to inject "security context" for each workload / service in my generated
compose.yaml
file.Today, I need to manually do that:
But when I have multiple workloads or containers, this is a bit painful.
A post-processing
yq
command may be able to help too, but same approach, not user friendly.Do we have an opportunity to introduce a new provisioner type (or something else) in order to patch a workload or a service directly in
score-compose generate
?The text was updated successfully, but these errors were encountered: