A node with subcomponents cannot be directly deleted via API
See original GitHub issueAccording to the change log, as of version 2.12
DELETE requests to a node detail will also delete all the node’s subcomponents
but that doesn’t appear to the case. When attempting to delete a project with a single subcomponent
curl -X DELETE "https://api.osf.io/v2/nodes/8xc9y/" -H "Authorization: Bearer $PAT"
the following error is thrown
{
"errors": [
{
"detail": "Any child components must be deleted prior to deleting this project."
}
],
"meta": {
"version": "2.0"
}
}
Am I missing something or misinterpret the docs?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
1905709 – Machine API deletion does not properly handle ...
SSH to a node in GCP cluster and run "sudo -i systemctl poweroff --force --force" 2. Delete machine via oc 3. Wait Expected:...
Read more >Delete error in CRUD RESTful API(Node.js , Express, Mongodb)
I am a complete beginner in Node.js , MongoDB and creating RESTful APIs The code given below is the function I am using...
Read more >can't add node after deleting it - Orion SDK
Agent is running, node exists. 2. Delete the node via API. Agent still running, still showing as connected on the Agent Management page....
Read more >Error on detach when Node created by subcomponent ...
This is a demonstration of issue 1 described in #3156 (comment) To see the error, open the developer console & refresh the page....
Read more >Watson Assistant v1 | IBM Cloud API Docs
The IBM Watson™ Assistant service combines machine learning, natural language understanding, and an integrated dialog editor to create conversation flows ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Changing
Accept-Header
toAccept
did the trick! Thanks!Ah, I think the header is supposed to be
Accept
and notAccept-Header
. We will need to change our documentation.