Skip to content

Use a connection pool for CRM requests in the API #3299

Use a connection pool for CRM requests in the API

Use a connection pool for CRM requests in the API #3299

Triggered via pull request October 17, 2024 13:20
Status Failure
Total duration 9m 25s
Artifacts

pr.yml

on: pull_request
Matrix: Tests
Lint
1m 37s
Lint
Validate Terraform
20s
Validate Terraform
Package application  /  Build & package
3m 23s
Package application / Build & package
Check for DQT integration changes
6s
Check for DQT integration changes
Deploy dev environment  /  Deploy to AKS
1m 9s
Deploy dev environment / Deploy to AKS
DQT integration tests
2m 24s
DQT integration tests
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 1 warning, and 1 notice
DQT integration tests
AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app '***'. Trace ID: c244e22b-531c-4805-a6eb-18cc02f51600 Correlation ID: b12b1442-24b2-491f-b1c9-164b0df7bc59 Timestamp: 2024-10-17 13:22:44Z
DQT integration tests
Interactive authentication is needed. Please run: az login
DQT integration tests
Login failed with Error: The process '/usr/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.
Deploy dev environment / Deploy to AKS
The following actions use a deprecated Node.js version and will be forced to run on node20: hashicorp/setup-terraform@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Lint
Linting changed files only