Software criado para pós graduação FIAP
- Project Description
- Coverage Status
- Run in Postman
- Miro Board for Event Storming and Storytelling
- Application Routes Documentation
- Database Documentation
- Installation
- Usage
- ZAP OWASP Scan
- License
ps: caso tenha problema para rodar os testes diretamente pelo link acima, a collection pode ser acessada tbm por este link ou ainda diretamente pelo arquivo neste link
obs: não esquecer de ativar o ambiente dev no postman
Download from https://github.com/kschltz/lanchonete
You can run/deploy the project in Kubernetes using the following command:
kubectl apply -f k8s/postgre/ && kubectl apply -f k8s/lanchonete/
If you are using minikube you can run the following helper script to start a fresh minikube and load everything you need:
./bin/minikube-ground-up.sh
It will:
- 1 - Delete the current minikube
- 2 - Create a new minikube
- 3 - build the app image
- 4 - load de image
- 5 - apply the k8s files
- 7 - enable the metrics addon
- 8 - open up minikube tunnel for connectivity
From the root of the project, run:
docker-compose up --build
Run the project in dev environment:
clojure -A:dev:test
Run the project directly, via :main-opts (-m mba-fiap.lanchonete):
clojure -M:run-m
Run the project's tests:
clojure -T:build test
Run the project's CI pipeline and build an uberjar:
clojure -T:build ci
This will produce an updated pom.xml file with synchronized dependencies inside the META-INF
directory inside target/classes and the uberjar in target. You can update the version (and SCM tag)
information in generated pom.xml by updating build.clj.
If you don't want the pom.xml file in your project, you can remove it. The ci task will
still generate a minimal pom.xml as part of the uber task, unless you remove version
from build.clj.
Run that uberjar:
java -jar target/lanchonete-0.1.0-SNAPSHOT.jar
Dentro da pasta /doc/zap temos um report gerado das rotas [POST] /pedido e [GET] /produtos/lanche após um scan do ZAP OWASP.
Não temos contexto no cenário atual do app de rotas expostas para pagamento, sendo assim, o contexto de pagamento não pode ser filtrado e analisado pelo ZAP OWASP.
Esse fluxo de pagamento está centralizado na arquitetura SAGA.
Copyright © 2023 Kschltz
EPLv1.0 is just the default for projects generated by clj-new: you are not
required to open source this project, nor are you required to use EPLv1.0!
Feel free to remove or change the LICENSE file and remove or update this
section of the README.md file!
Distributed under the Eclipse Public License version 1.0.