Skip to content

[DOCS-1166][DOCS-880][DOCS-1167][DOCS-1168] Update automation docs #1084

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 63 commits into from
Mar 31, 2025

Conversation

mdlinville
Copy link
Contributor

@mdlinville mdlinville commented Feb 5, 2025

@mdlinville mdlinville requested a review from a team as a code owner February 5, 2025 23:44
Copy link

cloudflare-workers-and-pages bot commented Feb 5, 2025

Deploying docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 803b7e2
Status: ✅  Deploy successful!
Preview URL: https://6e710725.docodile.pages.dev
Branch Preview URL: https://automation-updates.docodile.pages.dev

View logs

Copy link
Contributor

@ssisk ssisk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added some comments!

When we do add the docs for run metric events, they need a lot more explanation of how they work than what we have here - we should definitely meet at that time to walk through it

Copy link
Contributor

@tonyyli-wandb tonyyli-wandb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Partway through but have to step away, so wanted to leave any comments I have so far --

Co-authored-by: Stephen Sisk <[email protected]>
@mdlinville
Copy link
Contributor Author

See comments in-line.

I think it might be helpful to add some kind of diagram showing the event, action pair options. I attached one Raven originally created but we would want to update it to remove launch jobs and add notification.

Automation_event triggers action (2)

It would also be great if we added some more gifs, especially to the multi-step workflows that require you to navigate across parts of the app, like creating a webhook in team settings.

Captured for fast follow

@mdlinville
Copy link
Contributor Author

Still missing:

  • example payloads including github actions
  • structure of post request
  • test webhook endpoint
    but should be unblocked for run metrics notifications

The example payloads are not missing, we discussed offline. The other have been captured to https://wandb.atlassian.net/browse/DOCS-1379

Copy link
Contributor

@noaleetz noaleetz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

already approved but contains additional feedback to address

Specify the secrets you want to use for your webhook automation when you configure the webhook. See the [Configure a webhook]({{< relref "#configure-a-webhook" >}}) section for more information.

{{% alert %}}
Once you create a secret, you can access that secret in your W&B workflows with `$`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's not totally obvious how to use $ to access - I presume prefixing the name with $? Also, "W&B workflows" aren't really a thing - would automations be a more precise terminology?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I don't think I introduced this and I wasn't sure what it meant. Now updated.

1. Read the confirmation dialog, then click **Delete**. The secret is deleted immediately and permanently.

## Manage access to secrets
Each member of a team have access to its secrets. To revoke access to a secret from a particular member, remove that member from the team.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if no one can see the contents of a secret, and only admins can create/edit/delete them, what does it mean for a team member to have access to a secret?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, well a secret is a team-level asset. I guess it means that the team's automations get access to the secret. Let me try again.

From either of these pages, a Registry admin can manage existing automations:
- To view an automation's details, click its name.
- To edit an automation, click its action `...` menu, then click **Edit automation**.
- To delete an automation, click its action `...` menu, then click **Delete automation**. Confiruation is required.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does "configuration is required" mean here? I think we can get rid of that?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmation is required. Thanks!

From either of these pages, a Registry admin can manage existing automations:
- To view an automation's details, click its name.
- To edit an automation, click its action `...` menu, then click **Edit automation**.
- To delete an automation, click its action `...` menu, then click **Delete automation**. Confiruation is required.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmation is required. Thanks!

Comment on lines 126 to 127
| `${ACCESS_TOKEN}` | The value of the access token configured in the [webhook integration]({{< relref "#add-a-webhook-integration" >}}), if an access token is configured. The access token is automatically passed in the `Authorization: Bearer` HTTP header. |
| `${<SECRET>}` | If configured, the value of a secret configured in the [webhook integration]({{< relref "#add-a-webhook-integration" >}}). Replace `<SECRET>` with the name of the secret. |
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ssisk These were previously missing.

Specify the secrets you want to use for your webhook automation when you configure the webhook. See the [Configure a webhook]({{< relref "#configure-a-webhook" >}}) section for more information.

{{% alert %}}
Once you create a secret, you can access that secret in your W&B workflows with `$`.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I don't think I introduced this and I wasn't sure what it meant. Now updated.

1. Read the confirmation dialog, then click **Delete**. The secret is deleted immediately and permanently.

## Manage access to secrets
Each member of a team have access to its secrets. To revoke access to a secret from a particular member, remove that member from the team.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, well a secret is a team-level asset. I guess it means that the team's automations get access to the secret. Let me try again.

@mdlinville mdlinville requested a review from ngrayluna March 29, 2025 00:31
- Add missing Webhook and Slack Notification sections to Team Settings
- In both User and Team settings, note that wandb.alerts also requires an enterprise license

This page describes _automations_ in W&B. [Create an automation]({{< relref "create-automations/" >}}) to trigger workflow steps, such as automated model testing and deployment, based on an event in W&B, such as when an [artifact]({{< relref "/guides/core/artifacts" >}}) artifact version is created ({{< relref "/guides/core/registry/" >}}).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link incorrectly formatted.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

{{< readfile file="/_includes/enterprise-only.md" >}}
{{% /pageinfo %}}

An automation can run when a specific event occurs at a given scope, either a registry or a project. This page describes the events that can trigger an automation at each scope.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I try to avoid using "run" if it's not in the context of creating a run. (Unfortunate naming of an object).


This page describes _automations_ in W&B. [Create an automation]({{< relref "create-automations/" >}}) to trigger workflow steps, such as automated model testing and deployment, based on an event in W&B, such as when an [artifact]({{< relref "/guides/core/artifacts" >}}) artifact version is created ({{< relref "/guides/core/registry/" >}}).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@mdlinville mdlinville requested a review from ngrayluna March 31, 2025 21:28
@mdlinville mdlinville merged commit 8ca5621 into main Mar 31, 2025
4 checks passed
@mdlinville mdlinville deleted the automation_updates branch March 31, 2025 22:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants