You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/getting_started.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,14 +68,18 @@ CDK destroy can be run with ``make destroy``.
68
68
69
69
## **Preparing Code for PR**
70
70
71
-
Run ``make pr``. This command will run all the required checks, pre commit hooks, linters, code formatters, import sorting and tests, so you can be sure GitHub's pipeline will pass.
71
+
Run ``make pr``. This command will run all the required checks, pre commit hooks, linters, code formatters, import sorting and tests, so you can be sure GitHub's pipeline will pass. It will also generate an updated swagger OpenAPI JSON file and place it at docs/swagger/openapi.json location.
72
72
73
73
The command auto fixes errors in the code for you.
74
74
75
75
If there's an error in the pre-commit stage, it gets auto fixed. However, are required to run ``make pr`` again so it continues to the next stages.
76
76
77
77
Be sure to commit all the changes that ``make pr`` does for you.
78
78
79
+
## **OpenAPI Swagger Generation**
80
+
Run either ``make pr`` or ``make openopi`` to generate an updated swagger OpenAPI JSON file and place it at docs/swagger/openapi.json location.
81
+
82
+
79
83
## **GitHub Pages Documentation**
80
84
81
85
``make docs`` can be run to start a local HTTP server with the project's documentation pages.
Copy file name to clipboardExpand all lines: docs/pipeline.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,10 @@ All steps can be run locally using the makefile. See details below:
28
28
- Infrastructure test. Run `make infra-tests` to run the CDK infrastructure tests in the IDE
29
29
- Code coverage by [codecov.io](https://about.codecov.io/)
30
30
- Deploy CDK - run `make deploy` in the IDE, will also run security tests based on cdk_nag
31
+
- Integration tests - run `make integration` in the IDE.
31
32
- E2E tests - run `make e2e` in the IDE
32
33
- Code coverage tests - run `make coverage-tests` in the IDE after CDK dep
34
+
- OpenAPI Swagger file - run
33
35
- Update GitHub documentation branch
34
36
35
37
### **Other Capabilities**
@@ -49,11 +51,11 @@ The two most important ones are `pr-serverless-service` and `main-serverless-se
49
51
50
52
<imgalt="alt_text"src="../media/cicd_pr.png" />
51
53
52
-
`pr-serverless-service` runs for every pull request you open. It expects you defined a GitHub environment by the name `dev`and that it includes a secret by the name of `AWS_ROLE`.
54
+
`pr-serverless-service` runs for every pull request you open. It expects you defined a GitHub environments by the name `dev`, `staging`and `production` and for each environments to have the following variables: `CODECOV_TOKEN ` for CodeCov integration and `AWS_ROLE` that allows GitHub to deploy to that AWS account (one for dev, one for staging and one for production accounts).
53
55
54
56
It includes two jobs: 'quality_standards' and 'tests' where a failure in 'quality_standards' does not trigger 'tests'. Both jobs MUST pass in order to to be able to merge.
55
57
56
-
'quality_standards' includes all linters, pre-commit checks and units tests and 'tests' deploys the service to AWS, runs code coverage checks, security checks and E2E tests. Stack is destroyed at the end. Stack has a 'dev' prefix as part of its name.
58
+
'quality_standards' includes all linters, pre-commit checks and units tests and 'tests' deploys the service to AWS, runs code coverage checks, checks that your OpenAPI file is up to date and corresponds to the actual deployment (fails if it does not, hence your documentation is out of date), security checks and E2E tests. Stack is destroyed at the end. Stack has a 'dev' prefix as part of its name. Each environment has a pre-defined stack prefix.
0 commit comments