winvision / vsts-tasks Goto Github PK

When trying to create a collection in a serverless CosmosDb I get this error :

2021-03-10T04:32:56.3140412Z ##[error]Setting offer throughput or autopilot on container is not supported for serverless accounts.

I believe the "Throughput" setting in the task should be optional if one uses serverless version of CosmosDb to be used.

Hi, getting a strange error about a missing or undefined ResourceId. I can't seem to find any reference to the error in your code so I'm assuming it's a task library error being handled and forwarded on.

Considering there are only a few inputs in the agent task, none of which refer to a ResourceId, I'm not sure where to look.

I've checked the underlying connection string I'm passing in and it's valid, it looks like this:
"AccountEndpoint=https://myapp.documents.azure.com:443/;AccountKey=mykey;Database=mydbname;

I'm passing in the database name on the end of the conn string as I'd like that to be created before the collection is created.

Any ideas?

Hi,
Is there anyway to run this on a Linux agent or is there any workaround?

I am trying to migrate data from cosmos db collection to a json file in blob. I want to query the data as simple as "select * from c".

This works as expected when i run it from the copy migration tool locally (dev machine)

But when I add a VSTS task to do the same, I get the below mentioned error:

Command which is executing:
[command]C:\Damco1_work_tool\cosmosdt\1.7.0\x64\dt.exe /s:DocumentDB /s.ConnectionString:*** /s.Collection:RejectedBookingList "/s.Query:"SELECT RejectedBookingList.BookingNumber from RejectedBookingList"" /t:JsonFile /t.File:C:\Damco1_work\25\a\Order\rejectedbookinglist.json

ERROR Message:

Critical error: {"errors":[{"severity":"Error","location":{"start":0,"end":67},"code":"SC1001","message":"Syntax error, incorrect syntax near '"SELECT RejectedBookingList.BookingNumber from RejectedBookingList"'."}]}

I'm using the Data Migration Tool task to export data from a cosmos Db to another and get this error.
Have you seen or heard of this? What should I do?

Azure Cosmos DB Migration Tool Task fails with "Error: Parameter 'toolPath' cannot be null or empty."

running the release with System.Debug = true shows a 404 error when trying download the migration tool zip file:
2022-10-16T19:40:53.8790422Z ##[debug]Failed to download "5c797be1-b723-4cfc-889f-1267e3ae51c3" from "https://download.microsoft.com/download/E/1/4/E143A339-41AE-4E0E-9CC8-911C0B663478/dt-1.7.zip". Code(404) Message(Not Found)
2022-10-16T19:40:53.8793291Z ERR:Unexpected HTTP response: 404
2022-10-16T19:40:53.8793872Z ##[debug]task result: Failed

I opened the hints and reviewed the two screen shots in extensions page, but there is nothing tangible that shows how to configure the upload to a cosmosDB item/container.

What is the recommendation for creating the Cosmos DB that is required prior to creating / updating collections

I'm using the Create Collection task to create 6 collections over 3 different cosmos db accounts. This has functioned reliably for the past 12 months. Recently I will get a Resource Not Found error on 1 of the 6 collection creation tasks and the pipeline fails. The resource is clearly deployed - I probe the account to determine if the collection exists and set a condition that enables the creation task (creation task is skipped if the collection already exists). This feels like some sort of Azure issue.

Have you seen or heard reports of this?

tasklog_32.log

Hi, after figuring out how the connection string should look, I try to perform the creation of collection operation. The task gets stuck with the following message coming from the agent:

any ideas?

Describe the bug
Versions 1.0.18 and 1.0.19 cannot be executed in azure pipelines (the pipeline was successfully executed on version 1.0.13).
The displayed error is:
##[error]File not found: 'C:\agent_work_tasks\DataMigrationTool_bcb9bcd6-0dcc-4c3a-8e13-c900df4dd6d9\1.0.19\index.js'
Current agent version is '3.220.0'
The index.js is indeed missing in the _tasks folder. index.ts is present in the folder.

To Reproduce
Steps to reproduce the behavior:

1. Create a pipeline with Cosmos DB Data Migration Tool
2. Run the pipeline

Describe the bug
When running an azure devops release, a step with "Cosmos DB Data Migration" fails with the following error message:

2023-05-26T12:09:16.7410463Z (node:6476) Warning: Use Cipheriv for counter mode of aes-256-ctr
2023-05-26T12:09:18.6551975Z ERR:Unexpected HTTP response: 404
2023-05-26T12:09:18.6569867Z ##[error]Error: Parameter 'toolPath' cannot be null or empty.

digging a bit deeper, it seems, that the download is not reachable anymore:
Downloading: https://download.microsoft.com/download/E/1/4/E143A339-41AE-4E0E-9CC8-911C0B663478/dt-1.7.zip

(it did work until end of 2022)

To Reproduce
Steps to reproduce the behavior:

1. Create an azure devops release
2. create a step with "Cosmos DB Data Migration"
3. run the release
4. See error

Expected behavior
It should be possible to download the tool and run the "Cosmos DB Data Migration" step

Screenshots

Desktop (please complete the following information):

• Azure DevOps
• Browser: Chrome
• Version: latest

Hi, I am getting this error while doing data migration. I am taking a json file and updating the collection. Is there anything needs to be done from the pipeline?

I am using mongo API in cosmos. I think the issue occurs only when we use mongo API. is there something different I need provide in the connection string field?

I love the existing tool! My only issue is current the Azure Cosmos DB use port 443. The default for the current tool is 80.
So if you are using a deployment agent you will want to add the /t.ConnectionMode:Gateway parameter to connect to a Azure Cosmos DB using port 443. Currently there is not a way to add this parameter.

It would be great to have an option that creates the collection when it doesn't exist yet, but updates it when it does.

I found info online. I also follow the steps. However, the sample code throw the exception. I need some help on it.

The following is the doc I followed.

https://docs.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/oauth?toc=%2Fazure%2Fdevops%2Forganizations%2Ftoc.json&bc=%2Fazure%2Fdevops%2Forganizations%2Fbreadcrumb%2Ftoc.json&view=azure-devops#register-your-app

Hi I am using your task but currently getting error as I am not able to provide the json file path properly.
In my build Artifact I have the json file but how to set it not clear.
Can you please provide an example if possible

I faced the above problem, any idea?