Skip to content
Staging Deploy

open webuiを追加 #1524

Sign in to view logs

open webuiを追加

open webuiを追加 #1524

Triggered via pull request January 29, 2025 07:21
@piny940piny940
opened #1602
open-webui
Status Success
Total duration 2m 36s
Artifacts –

stg-deploy.yaml

on: pull_request
filter
5s
filter
kube-main
0s
kube-main
service-monitor-main
0s
service-monitor-main
fluxupd-main
0s
fluxupd-main
gcp-apply-main
0s
gcp-apply-main
aws-apply-main
0s
aws-apply-main
kube
4s
kube
service-monitor
0s
service-monitor
fluxupd
0s
fluxupd
gcp-apply
0s
gcp-apply
aws-apply
0s
aws-apply
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
@piny940
piny940
approved Jan 29, 2025
staging

Annotations

2 warnings
kube
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
kube
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).