-
Notifications
You must be signed in to change notification settings - Fork 3
Feature ETP-3459: Fixed local configurations and new make tasks #228
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
Open
Matias-Bernal
wants to merge
4
commits into
develop
Choose a base branch
from
feature/ETP-3459
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
071235d
Feature ETP-3459: Add auth bypass, Makefile, profiles
sebastianbarrozo 8f004de
Feature ETP-3459: Add loadtest and purge Makefile targets
sebastianbarrozo be950c8
Feature ETP-3459: Add EtendoRX platform technical docs
sebastianbarrozo e10a297
Feature ETP-3459: Fixed local configurations and new make tasks
Matias-Bernal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| # EtendoRX — Technical Documentation Index | ||
|
|
||
| EtendoRX is a reactive microservices platform built on **Spring Boot 3.1.4 / Spring Cloud 2022.0.4 / Java 17** for Etendo ERP integrations. It provides a composable runtime for data access, authentication, API routing, asynchronous task processing, and synchronization workflows. | ||
|
|
||
| --- | ||
|
|
||
| ## Service Catalog | ||
|
|
||
| | Service | Port | Purpose | | ||
| |---|---|---| | ||
| | Config Server | 8888 | Spring Cloud Config — centralized configuration for all services | | ||
| | Auth | 8094 | JWT authentication — token issuance and validation | | ||
| | DAS | 8092 | Data Access Service — REST API layer over the Etendo database | | ||
| | Edge | 8096 | API Gateway — routing, load balancing, and request filtering | | ||
| | AsyncProcess | 8099 | Async task processing — background job execution and scheduling | | ||
| | OBConnector Server | 8101 | Sync REST API — orchestration endpoint for synchronization flows | | ||
| | OBConnector Worker | 8102 | Sync execution engine — worker that executes sync pipeline steps | | ||
|
|
||
| --- | ||
|
|
||
| ## Platform Documentation | ||
|
|
||
| | Document | Description | | ||
| |---|---| | ||
| | [architecture.md](./architecture.md) | Platform architecture, service dependency graph, and service catalog with roles and responsibilities | | ||
| | [getting-started.md](./getting-started.md) | Prerequisites, local installation steps, environment setup, and first run walkthrough | | ||
| | [makefile-reference.md](./makefile-reference.md) | All build and deployment commands exposed through the project Makefile | | ||
| | [configuration.md](./configuration.md) | Configuration files, Spring Cloud Config properties, per-service overrides, and environment variables | | ||
| | [infrastructure.md](./infrastructure.md) | Docker Compose setup, Kafka and Redpanda message broker configuration, and Jaeger distributed tracing | | ||
|
|
||
| --- | ||
|
|
||
| ## Module Documentation | ||
|
|
||
| | Module | Index | | ||
| |---|---| | ||
| | OBConnector | [com.etendorx.integration.obconnector — Documentation Index](../modules/com.etendorx.integration.obconnector/docs/INDEX.md) | | ||
|
|
||
| --- | ||
|
|
||
| ## Diagrams | ||
|
|
||
| | File | Description | | ||
| |---|---| | ||
| | [00-async-process.plantuml](./00-async-process.plantuml) | Sequence diagram of the async process flow — job submission, worker pickup, and result handling | | ||
| | [01-async-deployment-diagram.plantuml](./01-async-deployment-diagram.plantuml) | Deployment diagram showing async infrastructure components and their relationships | |
Large diffs are not rendered by default.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion
Consider filtering the system properties to pass only those relevant to the application (e.g., using prefixes like 'spring.' or 'etendo.').
Rationale: Passing all system properties via
System.propertiesincludes internal JVM properties (e.g.,java.vm.version,user.dir,os.name) and environment-specific details that are generally not required by the Spring Boot application. Filtering these helps keep the child process environment clean and reduces the risk of accidental information exposure if the application logs its configuration.