Closed fmalykh closed 2 years ago
Thanks for the details. We'll have a look. Although, it might actually be an issue with xray.
Looks like we are missing repo_type = "remote"
in the JSON payload.
I was able to create a watch for remote repo using this payload:
{
"general_data": {
"name": "test-remote-repo-2",
"description": "This is a new watch created using API V2",
"active": true
},
"project_resources": {
"resources": [
{
"type": "repository",
"name": "npm-remote",
"bin_mgr_id": "default",
"repo_type": "remote"
}
]
},
"assigned_policies": [
{
"name": "Alex-OpRisk",
"type": "operational_risk"
}
]
}
}
But our code doesn't currently set repo_type
.
We could handle this for them - fetch the type and add it here. It would make it slower but would eliminate an issue.
Alternatively, force the user to decide and if there is an error, give a hint?
Wait.. this field only
applies if it's a repo type - otherwise no point.
Hi Team,
I'm getting 400 error when creating an
xray_watch
resource which includesremote
repositories.Here is a watch created manually through the GUI:
Now I successfully create the following
xray_watch
which contains local repository only:Then I try to add a remote repository:
Below are software versions: