Skip to content

CI/CD Production (1.56.0) #77

CI/CD Production (1.56.0)

CI/CD Production (1.56.0) #77

Re-run triggered February 26, 2025 17:47
Status Failure
Total duration 3m 51s
Artifacts 1

ci-cd-prod.yml

on: workflow_dispatch
Check if version exists
2s
Check if version exists
Get Latest Deployed Version Info from GitHub  /  Get Latest Deployed Versions from GitHub Variables
3s
Get Latest Deployed Version Info from GitHub / Get Latest Deployed Versions from GitHub Variables
Check for changes  /  Filter
6s
Check for changes / Filter
Deploy infra to prod  /  Deploy to prod
3m 17s
Deploy infra to prod / Deploy to prod
Deploy apps to prod  /  Deploy migration job to prod
2m 36s
Deploy apps to prod / Deploy migration job to prod
Store Latest Deployed Infra Version as GitHub Variable  /  Store GitHub Environment Variable
Store Latest Deployed Infra Version as GitHub Variable / Store GitHub Environment Variable
Matrix: Deploy apps to prod / deploy-apps
Matrix: Deploy apps to prod / deploy-jobs
publish-sdk-to-nuget  /  build-and-push
50s
publish-sdk-to-nuget / build-and-push
Store Latest Deployed Apps Version as GitHub Variable  /  Store GitHub Environment Variable
5s
Store Latest Deployed Apps Version as GitHub Variable / Store GitHub Environment Variable
Send Slack message on failure  /  Send Slack message
6s
Send Slack message on failure / Send Slack message
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 5 warnings
Deploy infra to prod / Deploy to prod
ERROR: {"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/***/providers/Microsoft.Resources/deployments/dp-be-prod-1.56.0","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"ResourceDeploymentFailure","target":"/subscriptions/***/resourceGroups/dp-be-prod-rg/providers/Microsoft.Resources/deployments/postgresql","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/***/resourceGroups/dp-be-prod-rg/providers/Microsoft.Resources/deployments/postgresql","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"InvalidParameterValue","message":"Invalid value given for parameter StandbyAvailabilityZone,availabilityZone. Specify a valid parameter value."}]}]}]}}
Deploy infra to prod / Deploy to prod
Error: Deployment failed.
Send Slack message on failure / Send Slack message
SlackError: An API error occurred: fatal_error
Deploy infra to prod / Deploy to prod
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 prod / Deploy to prod
This deployment mode is not supported for subscription scoped deployments, this parameter will be ignored!
Deploy infra to prod / Deploy to prod
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).