Replies: 1 comment 5 replies
-
I can't think of any valid reason to restrict that functionality in the condition of type File. Especially considering that we implemented similar behavior for other resources like json,toml,csv,etc. Maybe @hervelemeur recall something but I would bet on a lack of time or feature need at that time. If you feel comfortable with it, feel free to open a PR as I definitely see a need for that now that I started looking in github.com/updatecli/updatemonitor |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is there a reason why
spec:files > 1
isn't supported inconditions
ofkind: file
but is supported intargets
? Seeupdatecli/pkg/plugins/resources/file/condition.go
Lines 53 to 58 in 1c37a46
My use case is to simplify detection of patterns, for example, instead of doing this multiple times with
kind: "dockerfile"
, one for each file:We could simplify it with:
Because this functionality is already partially available in
kind: "file"
. Another option would be to add support tospec: files
tokind: "dockerfile"
, but this would require extra code.kind: "file"
withmatchpattern
is really powerful IMO.Beta Was this translation helpful? Give feedback.
All reactions