-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Improve Webhooks Documentation for Argo Workflows #14243
New issue
Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “No 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? No Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
ssganesh035
commented
Mar 3, 2025
- Enhanced clarity and structure for webhook configuration.
- Added detailed steps for setting up roles, service accounts, and secrets.
- Included a table for better readability of webhook parameters.
- Ensured Markdown formatting aligns with GitHub documentation standards.
Signed-off-by: Sudar Selva Ganesh M <117903686+ssganesh035@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this. As well as my comments, the PR title also needs updating and you need to run make docs
locally.
Ensured Markdown formatting aligns with GitHub documentation standards.
Signed-off-by: Sudar Selva Ganesh M <117903686+ssganesh035@users.noreply.github.com>
|
||
In the namespace that will receive the event, create [access token](access-token.md) resources for your client: | ||
To enable webhook-based event triggering, you need to configure authentication and authorization within the namespace that will receive the event. This involves setting up roles, service accounts, and secrets. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
each sentence on its own line please. See docs contribution guide.
This hasn't been done yet fyi. |