Replies: 6 comments 3 replies
-
See #749 (comment) |
Beta Was this translation helpful? Give feedback.
-
Yes, tried to put in diun.yml the following from the example to test:
But I got this in notification: Just a note, don't know if it's important: I use the following command to test: It seems that it does not iterate the metadatas... or that there are no metadatas. |
Beta Was this translation helpful? Give feedback.
-
I supposed about it and then I have another question... Can I force somehow the check on a container abount a new image availability or I have to wait for it? I am trying how to force this behaviour but I can't find a way... any advice is welcome :) |
Beta Was this translation helpful? Give feedback.
-
here it is:
|
Beta Was this translation helpful? Give feedback.
-
I confirm that "live" test worked. However I used the predefined "{{ .Entry.Metadata.ctn_names }}". My custom field {{ .Entry.Metadata.Container }} from label "diun.metadata.container=diun" do not work. I will investigate. |
Beta Was this translation helpful? Give feedback.
-
Seems there is a typo. Should be |
Beta Was this translation helpful? Give feedback.
-
I am trying to write in the notification (via PushOver) the container name where the image wa updated.
I use the following docker-compose.yaml file:
and this is the notif section in my diun.yml file:
Note the part "(container: {{ .Entry.Metadata.Container }})" at the end on templateBody.
Following is the message in the notification:
Docker tag docker.io/diun/testnotif:latest which you subscribed to through file provider is available on docker.io registry (container: ).
Note the part "(container: )" at the end of the message where I supposed there should be the container name from the field ".Entry.Metadata.Container".
Beta Was this translation helpful? Give feedback.
All reactions