Undelete Container API creates a new container - Githubissues

Azure / Azurite

A lightweight server clone of Azure Storage that simulates most of the commands supported by it with minimal dependencies

MIT License

1.8k stars 320 forks source link

Undelete Container API creates a new container #2318

Open cloudtest-anon opened 9 months ago

cloudtest-anon commented 9 months ago

Which service(blob, file, queue, table) does this issue concern?

Azure Blob

Which version of the Azurite was used?

3.21.0

Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)

npm

What's the Node.js version?

14.18.1

What problem was encountered?

Undelete container API does not behave correctly. A few scenarios of API violations:

When a container previously deleted is undeleted, the API generates an empty container with the same name rather than restoring its prior contents.
If attempting to undelete a container that was never deleted, the API generates an empty container with that name instead of indicating that it was never deleted.
The undelete container cloud API enforces strict verification for the "delete container version," while Azurite accepts any value for it.

From the logs, it looks like the create_container operation is performed against this API.

Steps to reproduce the issue?

Logs to reproduce the scenario 1: debug.log

EmmaZhu commented 9 months ago

Hi @anna-mazhar ,

Undelete container is not supported yet.

Older version Azurite cannot recognize container_restore request, it treat the request as a create request from the method and URI. Latest Azurite can recognize container_restore request, and can report "Current API is not implemented yet." error.

Can you please upgrade to the latest Azurite?

Thanks Emma