How do I delete an inaccessible repository?

[Rabbit]

So, I'm the bitbucket admin for my org, and I botched an import for a repo from a team member's personal workspace to the org project. I was able to import the repo once he gave me admin access to the version in his workspace, but the earlier attempt now appears in the repo list, and says it's not available when I click on it. Thus, I am not able to delete it in the normal way, or through curl. Here's the request I am sending: 

curl --location --request DELETE 'https://api.bitbucket.org/2.0/repositories/{workspace}/{bad_repo_slug}' \-
--header 'Authorization: Basic {key}'

 I am getting a 403 error in response to this, indicating that it just can't hit the endpoint, and auth isn't the issue (no 2fa enabled anyway). 

Is this a problem I can solve, or does this need to be handles on the atlassian side? I want to be able to rename the good repo to the name used by the bad one, but I can't do that as long as bitbucket thinks the name is taken.

[Theodora Boudale · Accepted solution]

Hello,

I could see in our system that the repo in question was stuck in 'Importing' mode with 0 data, so I went ahead and deleted it for you. When the import task fails and the repo is stuck in 'Importing' mode, then it can only be deleted from a member of Bitbucket Cloud support team.

If this ever occurs again, you can open a support ticket like you did via https://support.atlassian.com/contact/#/. It is also ok if you post your request here, if you feel comfortable sharing the repo URL publicly.

Please feel free to let me know if you have any questions!

Kind regards,
Theodora

[Rabbit]

Thanks! I appreciate it. 

[Michael March · Accepted solution]

There's something inconsistent on the Atlassian side for sure. 

If  you contact support, the should be able to free up that 'claim' on the project/repo name.

[Rabbit]

Sent a support ticket, let's see if that helps!

[Rabbit]

Accepted the answer, coz "Contact Support" was the right call. Thanks!