Ci: docker compose for local test scenario #24
Conversation
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
There was a problem hiding this comment.
KICS found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.
tom-rm-meyer-ISST
force-pushed
the
ci/local-deployment
branch
4 times, most recently
from
0f7a43a
to
c9e8572
Compare
tom-rm-meyer-ISST
force-pushed
the
ci/local-deployment
branch
from
c9e8572
to
3db608a
Compare
|
Quality check still fails because we need to incorporate this issue: eclipse-tractusx/sig-infra#230 |
|
Updated license headers. |
|
Regarding postgresql, remember to have a look at eclipse-tractusx/sig-infra#308 |
# Conflicts: # backend/src/main/java/org/eclipse/tractusx/puris/backend/stock/controller/ProductStockRequestApiController.java # backend/src/main/java/org/eclipse/tractusx/puris/backend/stock/logic/service/ProductStockRequestApiServiceImpl.java
|
Regarding quality checks: The TRG for base images only applies to publishing images. As we use it locally for integration test, it's fine. I added the exclusion already to the metadata file. As soon as the reusable workflow is ready, it will pass. See here. |
Release guideline workflow has been updated. Everything works out now! |
There was a problem hiding this comment.
LGTM, since it is only a local deployment for testing purposes and the KICS issues are addressed in #79
Description
Introduced a docker-compose for local test demonstration. Spins up following containers needed for edc 0.3.0
It provides additional setup scripts and configuration for the given scenario.
Please note: fixed the secrets and then squashed. Tried multiple times as one path was seen as secret. Externalized all potential secrets into an .env
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: