The Wayback Machine - https://web.archive.org/web/20230116081335/https://github.com/localstack/localstack/issues/7491
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request: implement DELETE /_localstack/ses endpoint #7491

Open
1 task done
ert78gb opened this issue Jan 13, 2023 · 1 comment
Open
1 task done

feature request: implement DELETE /_localstack/ses endpoint #7491

ert78gb opened this issue Jan 13, 2023 · 1 comment
Labels
aws:ses AWS Simple Email Service good first issue Good item to work on for newcomers status: triage needed LocalStack maintainers need to evaluate this issue type: feature Missing feature, like e.g. a service from a cloud provider

Comments

@ert78gb
Copy link

ert78gb commented Jan 13, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Feature description

Provide an URL where I can delete stored SES emails.
My motivation is to write integration tests much easier, if I could delete the stored emails from the localstack before each test case.

I use the docker image to run localstack. Mount the /var/lib/localstack folder to the host and delete the files from the tmp/state/ses is cumbersome because of the file permission issue of docker.

I think the simplest way to achieve the empty SES emails state is to implement a new endpoint in a same way as to the GET /_localstack/ses has been implemented:

path: /_localstack/ses
method: DELETE

🧑‍💻 Implementation

I am not a python developer, but I think one solution is to extend the SesServiceApiResource with an on_delete method.

Open question for me is either delete the /var/lib/localstack/tmp/state/ses folder or just delete the files of the ses folder.
The folder does not exist when the container starts. It is created when the first email received and saved by the service.
I think both solutions have the same performance impact, so the real question is what is preferred by the maintainers.

As I mentioned I am not familiar with python ecosystem but I am happy to help implementing the feature if you accept the request.

Anything else?

No response

@ert78gb ert78gb added status: triage needed LocalStack maintainers need to evaluate this issue type: feature Missing feature, like e.g. a service from a cloud provider labels Jan 13, 2023
@localstack-bot
Copy link
Collaborator

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.

@viren-nadkarni viren-nadkarni added aws:ses AWS Simple Email Service good first issue Good item to work on for newcomers labels Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws:ses AWS Simple Email Service good first issue Good item to work on for newcomers status: triage needed LocalStack maintainers need to evaluate this issue type: feature Missing feature, like e.g. a service from a cloud provider
Projects
None yet
Development

No branches or pull requests

3 participants