serverless-spy 0.0.49 → 0.0.50
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.jsii +16 -5
- package/README.md +23 -5
- package/dist/releasetag.txt +1 -1
- package/doc/CODE_OF_CONDUCT.md +20 -32
- package/doc/CONTRIBUTING.md +159 -0
- package/doc/concept.svg +249 -0
- package/doc/quick_start.md +1 -0
- package/lib/src/ServerlessSpy.js +1 -1
- package/package.json +14 -2
package/.jsii
CHANGED
|
@@ -3150,10 +3150,21 @@
|
|
|
3150
3150
|
"docs": {
|
|
3151
3151
|
"stability": "stable"
|
|
3152
3152
|
},
|
|
3153
|
-
"homepage": "
|
|
3153
|
+
"homepage": "https://serverlessspy.com",
|
|
3154
3154
|
"jsiiVersion": "1.69.0 (build f656c31)",
|
|
3155
3155
|
"keywords": [
|
|
3156
|
-
"cdk"
|
|
3156
|
+
"cdk",
|
|
3157
|
+
"aws",
|
|
3158
|
+
"testing",
|
|
3159
|
+
"jest",
|
|
3160
|
+
"serverless",
|
|
3161
|
+
"spy",
|
|
3162
|
+
"vitest",
|
|
3163
|
+
"lambda",
|
|
3164
|
+
"sqs",
|
|
3165
|
+
"sns",
|
|
3166
|
+
"dynamodb",
|
|
3167
|
+
"eventbridge"
|
|
3157
3168
|
],
|
|
3158
3169
|
"license": "MPL-2.0",
|
|
3159
3170
|
"metadata": {
|
|
@@ -3166,7 +3177,7 @@
|
|
|
3166
3177
|
},
|
|
3167
3178
|
"name": "serverless-spy",
|
|
3168
3179
|
"readme": {
|
|
3169
|
-
"markdown": "\n\
|
|
3180
|
+
"markdown": "\n\n# **DECLAREMENT: THE PROJECT IS IN THE DEEP DEVELOPMENT PHASE AND NOT JET MENT FOR USE.**\n\nCDK-based library for writing integration tests on AWS serverless architecture and web console to monitor events in real-time.\n\n# How it works\n\n**Add ServerlessSpy construct to your CDK stack, which creates infrastructure to intercept events in Lambda, SNS, SQS, EventBridge, DynamoDB... and send it to a testing library or your local web console via API Gateway websocket. The testing library subscribes to events so tests can be executed fast without checking/retrying if the event has been received. The testing library is integrated with Jest but can also be used with another library. The web console can be used to see and inspect events in real-time.**\n\n\n\n\n# What is not\n - ServerlessSpy can not be used if your infrastructure is not created with CDK.\n - The solution is meant for development and (automatic) testing environment only. You should **EXCLUDE** ServerlessSpy CDK construct in any other environment, especially production or high load. ServerlessSpy is not meant for those environments; it just induces costs and could contribute to hitting AWS quotas (Lambda concurrent executions, ...).\n\n# Documentation\n - [Quick start](doc/quick_start.md)\n - [Writing tests](doc/writing_tests.md)\n - Integrations\n - [Lambda](doc/lambda.md)\n - [SQS](doc/SQS.md)\n - [SNS](doc/SNS.md)\n - [EventBridge](doc/eventBridge.md)\n - [DynamoDB](doc/DynamoDB.md)\n - [Using web console](doc/web_console.md)\n - [Code of Conduct](doc/CODE_OF_CONDUCT.md)\n - [Contributing Guide](doc/CONTRIBUTING.md)"
|
|
3170
3181
|
},
|
|
3171
3182
|
"repository": {
|
|
3172
3183
|
"type": "git",
|
|
@@ -3543,6 +3554,6 @@
|
|
|
3543
3554
|
"symbolId": "src/ServerlessSpy:SpyFilter"
|
|
3544
3555
|
}
|
|
3545
3556
|
},
|
|
3546
|
-
"version": "0.0.
|
|
3547
|
-
"fingerprint": "
|
|
3557
|
+
"version": "0.0.50",
|
|
3558
|
+
"fingerprint": "9omCm8Qz9+zfGhwV3L77iENalgbHvoNw2zU3pPXVnzw="
|
|
3548
3559
|
}
|
package/README.md
CHANGED
|
@@ -1,11 +1,29 @@
|
|
|
1
1
|
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
# **DECLAREMENT: THE PROJECT IS IN THE DEEP DEVELOPMENT PHASE AND NOT JET MENT FOR USE.**
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
CDK-based library for writing integration tests on AWS serverless architecture and web console to monitor events in real-time.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
# How it works
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
**Add ServerlessSpy construct to your CDK stack, which creates infrastructure to intercept events in Lambda, SNS, SQS, EventBridge, DynamoDB... and send it to a testing library or your local web console via API Gateway websocket. The testing library subscribes to events so tests can be executed fast without checking/retrying if the event has been received. The testing library is integrated with Jest but can also be used with another library. The web console can be used to see and inspect events in real-time.**
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
|
|
12
|
+
|
|
13
|
+
|
|
14
|
+
# What is not
|
|
15
|
+
- ServerlessSpy can not be used if your infrastructure is not created with CDK.
|
|
16
|
+
- The solution is meant for development and (automatic) testing environment only. You should **EXCLUDE** ServerlessSpy CDK construct in any other environment, especially production or high load. ServerlessSpy is not meant for those environments; it just induces costs and could contribute to hitting AWS quotas (Lambda concurrent executions, ...).
|
|
17
|
+
|
|
18
|
+
# Documentation
|
|
19
|
+
- [Quick start](doc/quick_start.md)
|
|
20
|
+
- [Writing tests](doc/writing_tests.md)
|
|
21
|
+
- Integrations
|
|
22
|
+
- [Lambda](doc/lambda.md)
|
|
23
|
+
- [SQS](doc/SQS.md)
|
|
24
|
+
- [SNS](doc/SNS.md)
|
|
25
|
+
- [EventBridge](doc/eventBridge.md)
|
|
26
|
+
- [DynamoDB](doc/DynamoDB.md)
|
|
27
|
+
- [Using web console](doc/web_console.md)
|
|
28
|
+
- [Code of Conduct](doc/CODE_OF_CONDUCT.md)
|
|
29
|
+
- [Contributing Guide](doc/CONTRIBUTING.md)
|
package/dist/releasetag.txt
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
v0.0.
|
|
1
|
+
v0.0.50
|
package/doc/CODE_OF_CONDUCT.md
CHANGED
|
@@ -1,16 +1,13 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Code of Conduct - ServerlessSpy
|
|
2
2
|
|
|
3
3
|
## Our Pledge
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
and orientation.
|
|
11
|
-
|
|
12
|
-
We pledge to act and interact in ways that contribute to an open, welcoming,
|
|
13
|
-
diverse, inclusive, and healthy community.
|
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
|
6
|
+
contributors and maintainers pledge to make participation in our project and
|
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
|
8
|
+
size, disability, ethnicity, sex characteristics, gender identity and expression,
|
|
9
|
+
level of experience, education, socio-economic status, nationality, personal
|
|
10
|
+
appearance, race, religion, or sexual identity and orientation.
|
|
14
11
|
|
|
15
12
|
## Our Standards
|
|
16
13
|
|
|
@@ -28,7 +25,7 @@ community include:
|
|
|
28
25
|
Examples of unacceptable behavior include:
|
|
29
26
|
|
|
30
27
|
* The use of sexualized language or imagery, and sexual attention or
|
|
31
|
-
advances
|
|
28
|
+
advances
|
|
32
29
|
* Trolling, insulting or derogatory comments, and personal or political attacks
|
|
33
30
|
* Public or private harassment
|
|
34
31
|
* Publishing others' private information, such as a physical or email
|
|
@@ -36,17 +33,17 @@ Examples of unacceptable behavior include:
|
|
|
36
33
|
* Other conduct which could reasonably be considered inappropriate in a
|
|
37
34
|
professional setting
|
|
38
35
|
|
|
39
|
-
##
|
|
36
|
+
## Our Responsibilities
|
|
40
37
|
|
|
41
|
-
|
|
38
|
+
Project maintainers are responsible for clarifying and enforcing our standards of
|
|
42
39
|
acceptable behavior and will take appropriate and fair corrective action in
|
|
43
|
-
response to any behavior that they deem inappropriate,
|
|
44
|
-
or harmful.
|
|
40
|
+
response to any behavior that they deem inappropriate,
|
|
41
|
+
threatening, offensive, or harmful.
|
|
45
42
|
|
|
46
|
-
|
|
43
|
+
Project maintainers have the right and responsibility to remove, edit, or reject
|
|
47
44
|
comments, commits, code, wiki edits, issues, and other contributions that are
|
|
48
|
-
not aligned to this Code of Conduct, and will
|
|
49
|
-
decisions when appropriate.
|
|
45
|
+
not aligned to this Code of Conduct, and will
|
|
46
|
+
communicate reasons for moderation decisions when appropriate.
|
|
50
47
|
|
|
51
48
|
## Scope
|
|
52
49
|
|
|
@@ -59,8 +56,7 @@ representative at an online or offline event.
|
|
|
59
56
|
## Enforcement
|
|
60
57
|
|
|
61
58
|
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
62
|
-
reported to the community leaders responsible for enforcement at
|
|
63
|
-
.
|
|
59
|
+
reported to the community leaders responsible for enforcement at <marko@serverlesslife.com>.
|
|
64
60
|
All complaints will be reviewed and investigated promptly and fairly.
|
|
65
61
|
|
|
66
62
|
All community leaders are obligated to respect the privacy and security of the
|
|
@@ -114,15 +110,7 @@ the community.
|
|
|
114
110
|
|
|
115
111
|
## Attribution
|
|
116
112
|
|
|
117
|
-
This Code of Conduct is adapted from the [Contributor Covenant]
|
|
118
|
-
version
|
|
119
|
-
https://www.contributor-covenant.org/version/2/0/code_of_conduct.
|
|
120
|
-
|
|
121
|
-
Community Impact Guidelines were inspired by [Mozilla's code of conduct
|
|
122
|
-
enforcement ladder](https://github.com/mozilla/diversity).
|
|
123
|
-
|
|
124
|
-
[homepage]: https://www.contributor-covenant.org
|
|
125
|
-
|
|
126
|
-
For answers to common questions about this code of conduct, see the FAQ at
|
|
127
|
-
https://www.contributor-covenant.org/faq. Translations are available at
|
|
128
|
-
https://www.contributor-covenant.org/translations.
|
|
113
|
+
This Code of Conduct is adapted from the [Contributor Covenant](https://contributor-covenant.org/), version
|
|
114
|
+
[1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct/code_of_conduct.md) and
|
|
115
|
+
[2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/code_of_conduct.md),
|
|
116
|
+
and was generated by [contributing-gen](https://github.com/bttger/contributing-gen).
|
|
@@ -0,0 +1,159 @@
|
|
|
1
|
+
<!-- omit in toc -->
|
|
2
|
+
# Contributing to ServerlessSpy
|
|
3
|
+
|
|
4
|
+
First off, thanks for taking the time to contribute! ❤️
|
|
5
|
+
|
|
6
|
+
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
|
|
7
|
+
|
|
8
|
+
> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
|
|
9
|
+
> - Star the project
|
|
10
|
+
> - Tweet about it
|
|
11
|
+
> - Refer this project in your project's readme
|
|
12
|
+
> - Mention the project at local meetups and tell your friends/colleagues
|
|
13
|
+
|
|
14
|
+
<!-- omit in toc -->
|
|
15
|
+
## Table of Contents
|
|
16
|
+
|
|
17
|
+
- [Code of Conduct](#code-of-conduct)
|
|
18
|
+
- [I Have a Question](#i-have-a-question)
|
|
19
|
+
- [I Want To Contribute](#i-want-to-contribute)
|
|
20
|
+
- [Reporting Bugs](#reporting-bugs)
|
|
21
|
+
- [Suggesting Enhancements](#suggesting-enhancements)
|
|
22
|
+
- [Your First Code Contribution](#your-first-code-contribution)
|
|
23
|
+
- [Improving The Documentation](#improving-the-documentation)
|
|
24
|
+
- [Styleguides](#styleguides)
|
|
25
|
+
- [Commit Messages](#commit-messages)
|
|
26
|
+
- [Join The Project Team](#join-the-project-team)
|
|
27
|
+
|
|
28
|
+
|
|
29
|
+
## Code of Conduct
|
|
30
|
+
|
|
31
|
+
This project and everyone participating in it is governed by the
|
|
32
|
+
[ServerlessSpy Code of Conduct](https://github.com/ServerlessLife/serverless-spyblob/master/CODE_OF_CONDUCT.md).
|
|
33
|
+
By participating, you are expected to uphold this code. Please report unacceptable behavior
|
|
34
|
+
to <marko@serverlesslife.com>.
|
|
35
|
+
|
|
36
|
+
|
|
37
|
+
## I Have a Question
|
|
38
|
+
|
|
39
|
+
> If you want to ask a question, we assume that you have read the available [Documentation](https://serverlessspy.com/).
|
|
40
|
+
|
|
41
|
+
Before you ask a question, it is best to search for existing [Issues](https://github.com/ServerlessLife/serverless-spy/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
|
|
42
|
+
|
|
43
|
+
If you then still feel the need to ask a question and need clarification, we recommend the following:
|
|
44
|
+
|
|
45
|
+
- Open an [Issue](https://github.com/ServerlessLife/serverless-spy/issues/new).
|
|
46
|
+
- Provide as much context as you can about what you're running into.
|
|
47
|
+
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
|
|
48
|
+
|
|
49
|
+
We will then take care of the issue as soon as possible.
|
|
50
|
+
|
|
51
|
+
<!--
|
|
52
|
+
You might want to create a separate issue tag for questions and include it in this description. People should then tag their issues accordingly.
|
|
53
|
+
|
|
54
|
+
Depending on how large the project is, you may want to outsource the questioning, e.g. to Stack Overflow or Gitter. You may add additional contact and information possibilities:
|
|
55
|
+
- IRC
|
|
56
|
+
- Slack
|
|
57
|
+
- Gitter
|
|
58
|
+
- Stack Overflow tag
|
|
59
|
+
- Blog
|
|
60
|
+
- FAQ
|
|
61
|
+
- Roadmap
|
|
62
|
+
- E-Mail List
|
|
63
|
+
- Forum
|
|
64
|
+
-->
|
|
65
|
+
|
|
66
|
+
## I Want To Contribute
|
|
67
|
+
|
|
68
|
+
> ### Legal Notice <!-- omit in toc -->
|
|
69
|
+
> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
|
|
70
|
+
|
|
71
|
+
### Reporting Bugs
|
|
72
|
+
|
|
73
|
+
<!-- omit in toc -->
|
|
74
|
+
#### Before Submitting a Bug Report
|
|
75
|
+
|
|
76
|
+
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
|
|
77
|
+
|
|
78
|
+
- Make sure that you are using the latest version.
|
|
79
|
+
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://serverlessspy.com/). If you are looking for support, you might want to check [this section](#i-have-a-question)).
|
|
80
|
+
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/ServerlessLife/serverless-spyissues?q=label%3Abug).
|
|
81
|
+
- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
|
|
82
|
+
- Collect information about the bug:
|
|
83
|
+
- Stack trace (Traceback)
|
|
84
|
+
- OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
|
|
85
|
+
- Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
|
|
86
|
+
- Possibly your input and the output
|
|
87
|
+
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
|
|
88
|
+
|
|
89
|
+
<!-- omit in toc -->
|
|
90
|
+
#### How Do I Submit a Good Bug Report?
|
|
91
|
+
|
|
92
|
+
> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to <marko@serverlesslife.com>.
|
|
93
|
+
<!-- You may add a PGP key to allow the messages to be sent encrypted as well. -->
|
|
94
|
+
|
|
95
|
+
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
|
|
96
|
+
|
|
97
|
+
- Open an [Issue](https://github.com/ServerlessLife/serverless-spy/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
|
|
98
|
+
- Explain the behavior you would expect and the actual behavior.
|
|
99
|
+
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
|
|
100
|
+
- Provide the information you collected in the previous section.
|
|
101
|
+
|
|
102
|
+
Once it's filed:
|
|
103
|
+
|
|
104
|
+
- The project team will label the issue accordingly.
|
|
105
|
+
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
|
|
106
|
+
- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
|
|
107
|
+
|
|
108
|
+
<!-- You might want to create an issue template for bugs and errors that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->
|
|
109
|
+
|
|
110
|
+
|
|
111
|
+
### Suggesting Enhancements
|
|
112
|
+
|
|
113
|
+
This section guides you through submitting an enhancement suggestion for ServerlessSpy, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
|
|
114
|
+
|
|
115
|
+
<!-- omit in toc -->
|
|
116
|
+
#### Before Submitting an Enhancement
|
|
117
|
+
|
|
118
|
+
- Make sure that you are using the latest version.
|
|
119
|
+
- Read the [documentation](https://serverlessspy.com/) carefully and find out if the functionality is already covered, maybe by an individual configuration.
|
|
120
|
+
- Perform a [search](https://github.com/ServerlessLife/serverless-spy/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
|
|
121
|
+
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
|
|
122
|
+
|
|
123
|
+
<!-- omit in toc -->
|
|
124
|
+
#### How Do I Submit a Good Enhancement Suggestion?
|
|
125
|
+
|
|
126
|
+
Enhancement suggestions are tracked as [GitHub issues](https://github.com/ServerlessLife/serverless-spy/issues).
|
|
127
|
+
|
|
128
|
+
- Use a **clear and descriptive title** for the issue to identify the suggestion.
|
|
129
|
+
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
|
|
130
|
+
- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
|
|
131
|
+
- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux. <!-- this should only be included if the project has a GUI -->
|
|
132
|
+
- **Explain why this enhancement would be useful** to most ServerlessSpy users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
|
|
133
|
+
|
|
134
|
+
<!-- You might want to create an issue template for enhancement suggestions that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->
|
|
135
|
+
|
|
136
|
+
### Your First Code Contribution
|
|
137
|
+
<!-- TODO
|
|
138
|
+
include Setup of env, IDE and typical getting started instructions?
|
|
139
|
+
|
|
140
|
+
-->
|
|
141
|
+
|
|
142
|
+
### Improving The Documentation
|
|
143
|
+
<!-- TODO
|
|
144
|
+
Updating, improving and correcting the documentation
|
|
145
|
+
|
|
146
|
+
-->
|
|
147
|
+
|
|
148
|
+
## Styleguides
|
|
149
|
+
### Commit Messages
|
|
150
|
+
<!-- TODO
|
|
151
|
+
|
|
152
|
+
-->
|
|
153
|
+
|
|
154
|
+
## Join The Project Team
|
|
155
|
+
<!-- TODO -->
|
|
156
|
+
|
|
157
|
+
<!-- omit in toc -->
|
|
158
|
+
## Attribution
|
|
159
|
+
This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)!
|