Hello all. Creating a new thread per @thankful-minister-83577's suggestion since the old one was getting a bit long: https://flyte-org.slack.com/archives/CP2HDHKE1/p1692713851511769 Having some trouble building a helm chart for flyte-binary for SNS notifications: This format does indeed at least attempt to access your queue and topic for `flyte-binary`:

configuration:
  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

).

oh this thing

We’re using helmfile but yeah it’s essentially equivalent, when we run helmfile sync or helmfile apply we see this error

i think this is just escaping the braces correctly right?

Awesome, this worked! Posting this so it can help others:

emailer:
  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 {{ "}}" }}

please follow up if you ever figure out the b64 stuff. i am super confused esp given the debugging output we saw

I certainly will. I still don’t understand why test messages aren’t coming in base64 encoded but the ones from Flyte do, tentatively hopeful that a simple Lambda function can decode it before passing it along

not really sure what you mean by lambda functions.

Gotcha, that's what I thought but just wanted to confirm. (You can use Lambda to run code snippets when events occur like an email entering a queue for example.) Glad my assumption there was correct.

@high-accountant-32689 or @glamorous-carpet-83516 any ideas?