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

Add option to disable dead letter queue #711

Conversation

m9rc1n
Copy link
Contributor

@m9rc1n m9rc1n commented May 15, 2023

No description provided.

@NoxHarmonium
Copy link
Collaborator

Hi @m9rc1n, thanks for the contribution!

Out of curiosity, what was the reason you needed to disable the DLQ in the project you were using this plugin? Was it just for simplicity or did you want to bring your own DLQ or something like that?

It looks like the tests are failing because we are no longer hitting our test coverage target after adding the new branches. Would it be possible to write a test that confirms that the DLQ and associated IAM policies are not created when that attribute is set to false?

There should be some examples in https://github.com/agiledigital/serverless-sns-sqs-lambda/blob/master/lib/serverless-sns-sqs-lambda.test.ts#L566
It should be as simple as adding a snapshot of the relevant area of the template.

@m9rc1n
Copy link
Contributor Author

m9rc1n commented May 18, 2023

Hi @NoxHarmonium,

Thanks for your reply.
We are using your plugin at my current workplace and we decided to resign from DLQ to reduce costs mostly (+ simplicity).

I will add tests and will get back to you shortly!
Marcin

@m9rc1n m9rc1n force-pushed the add-option-to-disable-dead-letter-queue branch from 5d1c457 to 12a694b Compare May 18, 2023 21:02
@m9rc1n
Copy link
Contributor Author

m9rc1n commented May 18, 2023

Hi,

Test added 👍🏻

@m9rc1n
Copy link
Contributor Author

m9rc1n commented May 23, 2023

@NoxHarmonium could you check my MR? Tests were added but still not running. I have 1 more MR to publish

@NoxHarmonium
Copy link
Collaborator

Sorry for the delay @m9rc1n. Tests are passing and the change LGTM. I'll merge it now.

@NoxHarmonium NoxHarmonium merged commit 06a0dfb into agiledigital:master May 23, 2023
4 checks passed
@NoxHarmonium
Copy link
Collaborator

Oh I forgot to check that the commits were in the right format for semantic release (e.g. https://www.conventionalcommits.org/en/v1.0.0/#summary)

I'll force a release this time, but in the future commits should follow that standard

NoxHarmonium added a commit that referenced this pull request May 24, 2023
- The original commits in PR #711 didn't follow the conventions needed
  for semantic release to do its job, so this should force the change to
  be included.
NoxHarmonium pushed a commit that referenced this pull request May 24, 2023
# [2.1.0](v2.0.1...v2.1.0) (2023-05-24)

### Features

* empty commit to force release of [#711](#711) ([b090fa7](b090fa7))
@NoxHarmonium
Copy link
Collaborator

🎉 This PR is included in version 2.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@m9rc1n
Copy link
Contributor Author

m9rc1n commented Jun 12, 2023

Sure @NoxHarmonium, thanks for fixing it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants