Hello
I’m associating a webhook automation to my model registry artifacts, that makes a request to a Dagster server and calls our internal pipelines using the artifact’s metadata.
I know that I can access WandB from the Dagster side and retrieve the necessary metadata. However, it would be cleaner for our use case that that metadata was within the payload.
Basically, what I’m missing is being able to send the s3_uri (associated with the artifact’s file). In the docs, there are several payloads variables like ${artifact_version_string} , while hinting there could be more.
Where can we find a list of all available payload variables? And is there a way to send the corresponding s3_uri through the webhook automation?
Thank you!
Hey @ruippmendes, thanks for writing in! Just to make sure I understand your use-case, you’re creating a model artifact that references an s3 file and would like to access that uri in the automation, is this correct?
hey @luis_bergua , thanks for the quick reply!
We have several model artifacts, each with a reference to an s3 file. I added a webhook automation that calls Dagster. I wanted to know how to send that reference (URI to the s3 file) through the webhook request.
In Artifact automations | Weights & Biases Documentation (wandb.ai) , there are a couple of example payload parameters that can be sent through the webhook (like ${artifact_version_string}), which can be used to access the artifact from the Dagster side, which is also a good solution for us. But just for information, are there more parameters (relative to the artifact itself) that can be sent through the webhook payload?
Hey @ruippmendes, thanks for sharing this information and apologies for the delay. After checking internally, it seems the variables in the docs are the ones available so the s3 URI isn’t accesible. I’ll be happy to create a feature request for you if you want, just let me know!
Hi Rui, I wanted to follow up on this request. Please let us know if we can be of further assistance or if your issue has been resolved.
Hi Rui, since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!
Hey Rui! We recently shipped a feature that lets you pass in a metadata field from the metadata attached to the given artifact version into the automations payload and thought this would be helpful for your use case as you could add the S3 URI to the metadata and pass it.
