chore(ci): Add missing method parameter when sending Slack message (#… #868
ci-cd-main.yml
on: push
Check for changes
/
Filter
4s
Generate git short sha
/
Generate git short sha
2s
Get current version
/
Filter
2s
Release please
11s
Deploy slack notifier (test)
/
Build and deploy slack-notifier to test
1m 2s
Matrix: Build and publish docker images / publish-docker-images
Matrix: Deploy apps to test / deploy-apps
Waiting for pending jobs
Matrix: Deploy apps to test / deploy-jobs
Waiting for pending jobs
Deploy schema npm package
/
check-published-version
Send Slack message on failure
/
Send Slack message
3s
Annotations
3 errors and 9 warnings
Deploy infra to test / Deploy to test
WARNING: /home/runner/work/dialogporten/dialogporten/.azure/modules/functionApp/slackNotifier.bicep(69,9) : Warning BCP334: The provided value can have a length as small as 0 and may be too short to assign to a target with a configured minimum length of 3. [https://aka.ms/bicep/core-diagnostics#BCP334]
|
Deploy infra to test / Deploy to test
ERROR: AADSTS700024: Client assertion is not within its valid time range. Current time: 2024-11-29T23:12:38.8157188Z, assertion valid from 2024-11-29T22:17:36.0000000Z, expiry time of assertion 2024-11-29T22:22:36.0000000Z. Review the documentation at https://learn.microsoft.com/entra/identity-platform/certificate-credentials . Trace ID: a7cd4245-fec5-4004-b527-4e0fbbe99f00 Correlation ID: 37e1add6-c77d-41e4-8d9e-6279484fa521 Timestamp: 2024-11-29 23:12:38Z
|
Deploy infra to test / Deploy to test
Error: Deployment failed.
|
Legacy key/value format with whitespace separator should not be used:
src/Digdir.Domain.Dialogporten.Infrastructure/MigrationBundle.dockerfile#L8
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals:
src/Digdir.Domain.Dialogporten.Infrastructure/MigrationBundle.dockerfile#L33
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals
More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
|
Deploy infra to test / Deploy to test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Deploy infra to test / Deploy to test
This deployment mode is not supported for subscription scoped deployments, this parameter will be ignored!
|
Deploy infra to test / Deploy to test
WARNING: The configuration value of bicep.use_binary_from_path has been set to 'false'.
|
Deploy infra to test / Deploy to test
WARNING: /home/runner/work/dialogporten/dialogporten/.azure/modules/functionApp/slackNotifier.bicep(69,9) : Warning BCP334: The provided value can have a length as small as 0 and may be too short to assign to a target with a configured minimum length of 3. [https://aka.ms/bicep/core-diagnostics#BCP334]
|
Deploy infra to test / Deploy to test
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Send Slack message on failure / Send Slack message
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.
|
Send Slack message on failure / Send Slack message
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).
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
digdir~dialogporten~6HFTKN.dockerbuild
|
42.7 KB |
|
digdir~dialogporten~98A1HQ.dockerbuild
|
40.8 KB |
|
digdir~dialogporten~9AXMBE.dockerbuild
|
41.7 KB |
|
digdir~dialogporten~GSRWFZ.dockerbuild
|
42.6 KB |
|
digdir~dialogporten~JNLXSL.dockerbuild
|
42.5 KB |
|
digdir~dialogporten~ZIY368.dockerbuild
|
40.9 KB |
|