Skip to content

Update to Azure Cosmos DB extension 4.x #21

Update to Azure Cosmos DB extension 4.x

Update to Azure Cosmos DB extension 4.x #21

Triggered via push October 17, 2023 13:31
Status Failure
Total duration 4m 45s
Artifacts

backend.main.yml

on: push
build-and-deploy
4m 29s
build-and-deploy
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 1 warning
build-and-deploy: backend/api/GetResumeCounter.cs#L21
The type or namespace name 'id' could not be found (are you missing a using directive or an assembly reference?)
build-and-deploy: backend/api/GetResumeCounter.cs#L21
The type or namespace name 'partitionKey' could not be found (are you missing a using directive or an assembly reference?)
build-and-deploy: backend/api/GetResumeCounter.cs#L20
The type or namespace name 'id' could not be found (are you missing a using directive or an assembly reference?)
build-and-deploy: backend/api/GetResumeCounter.cs#L20
The type or namespace name 'partitionKey' could not be found (are you missing a using directive or an assembly reference?)
build-and-deploy: backend/api/GetResumeCounter.cs#L21
The type or namespace name 'id' could not be found (are you missing a using directive or an assembly reference?)
build-and-deploy: backend/api/GetResumeCounter.cs#L21
The type or namespace name 'partitionKey' could not be found (are you missing a using directive or an assembly reference?)
build-and-deploy: backend/api/GetResumeCounter.cs#L20
The type or namespace name 'id' could not be found (are you missing a using directive or an assembly reference?)
build-and-deploy: backend/api/GetResumeCounter.cs#L20
The type or namespace name 'partitionKey' could not be found (are you missing a using directive or an assembly reference?)
build-and-deploy
Process completed with exit code 1.
build-and-deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/