Peter Klingelhofer
09/27/2023, 2:51 PMconfiguration:
inline:
notifications:
type: "aws"
region: "us-east-1"
publisher:
topicName: "arn:aws:sns:us-east-1:#########:some-name"
processor:
queueName: "some-name"
accountId: "#########"
emailer:
sender: "<mailto:email@address.com|email@address.com>"
subject: "hi this is the email subject"
body: "hi this is the email body"
Unfortunately if we switch to the more complex syntax (with `{{ workflow }}`or any of the other template literal variables) (as seen in the docs: https://docs.flyte.org/en/latest/deployment/configuration/notifications.html#config), we still see function "workflow" not defined
errors (parse error at (flyte-binary/templates/deployment.yaml:4): function "workflow" not defined
).Yee
helm template
command right?Peter Klingelhofer
09/27/2023, 4:01 PMYee
Peter Klingelhofer
09/27/2023, 4:39 PMemailer:
sender: "<mailto:email@address.com|email@address.com>"
subject: 'Notice: Execution "{{ "{{" }} workflow.name {{ "}}" }}" has {{ "{{" }} phase {{ "}}" }} in "{{ "{{" }} domain {{ "}}" }}".'
body: >
Execution "{{ "{{" }} workflow.name {{ "}}" }} [{{ "{{" }} name {{ "}}" }}]" has {{ "{{" }} phase {{ "}}" }} in "{{ "{{" }} domain {{ "}}" }}". View details at
<a href=<http://localhost:8088/console/projects/{{> "{{" }} project {{ "}}" }}/domains/{{ "{{" }} domain {{ "}}" }}/executions/{{ "{{" }} name {{ "}}" }}>
<http://localhost:8088/console/projects/{{> "{{" }} project {{ "}}" }}/domains/{{ "{{" }} domain {{ "}}" }}/executions/{{ "{{" }} name {{ "}}" }}</a>. {{ "{{" }} error {{ "}}" }}
Yee
Peter Klingelhofer
09/27/2023, 7:05 PMYee
Peter Klingelhofer
10/02/2023, 4:40 PMYee