This change aligns the CI workflow with the current development branch naming convention, ensuring that the Docker image is built and pushed for development tags.
Refactored multiple files to use LocalDateTimeUtil.now() instead of LocalDateTime.now(). This ensures consistent timezone handling across the application by leveraging the centralized utility method.
Add new podman scripts for running database, Grafana, and Elasticsearch services on Aliyun. Update logback configuration to remove traceId and spanId from log patterns. Delete outdated run_elasticsearch.sh script as it is no longer needed.
The APM service port has been updated from 8200 to 9300 across all Dockerfiles to align with the new configuration. Additionally, the exposed port 8200 has been removed from the docker-compose files as it is no longer needed. This change ensures consistency and reduces unnecessary port exposure.
This commit fixes incorrect file paths in README.md and application.yml files, ensuring consistency in naming conventions. Additionally, it adds GC logging configuration to Dockerfiles across multiple modules to enable detailed garbage collection logging for better debugging and performance monitoring.
The `-XX:+UseG1GC` and `-Djava.security.egd=file:/dev/./urandom` flags in the `JAVA_OPS` environment variable were reordered across multiple Dockerfiles to maintain a consistent configuration. This change improves readability and ensures uniformity in the application's runtime settings.
Add Logstash Logback dependency to enable JSON logging and update the logback.xml configuration to include a JSON encoder. Also, update the CI workflow to cache Maven packages and improve build performance by disabling transfer progress.
The GC_LOG environment variable and its usage in the CMD instruction have been removed from all Dockerfiles to streamline the container startup process. This change reduces complexity and aligns with a simplified logging strategy.
Additionally, the docker-compose-elasticsearch.yml and docker-compose-elasticsearch-aliyun.yml files have been updated to reorder services, add Java options for Elasticsearch and Logstash, and ensure proper service dependencies.
- Consolidate SQL query formatting in DeviceStatusHistoryMapper.xml and DriverStatusHistoryMapper.xml
- Update application.yml with undertow access log configuration
- Enhance readability of descriptions in pom.xml files
Reordered the `WORKDIR` and `RUN` commands in multiple Dockerfiles to ensure a more logical and consistent structure. This improves readability and maintainability of the Dockerfiles.
Added two docker-compose files to configure Elasticsearch, Kibana, and Logstash services. The first file is for a standard setup, while the second is tailored for Aliyun's container registry. This change facilitates easier deployment and testing of the Elasticsearch stack in different environments.
Updated the descriptions in the pom.xml files for various DC3 platform modules to provide clearer and more detailed explanations of their functionalities. This improves the understanding of each module's purpose and capabilities.
Restructured MongoDB configuration and repository service to improve maintainability and clarity. Updated dependency management, added new MongoDB-specific classes, and corrected configuration files. This refactor ensures better organization and alignment with the project's architecture.
This commit replaces InfluxDB with MongoDB as the primary storage solution for point values. The changes include:
- Removal of all InfluxDB-related code, including configuration, entities, and repository implementation
- Addition of MongoDB configuration, entities, and repository service
- Implementation of MongoDB-specific indexing and query operations for point value storage and retrieval
- Update of Spring configuration and factory patterns to support MongoDB integration
The migration to MongoDB provides better scalability and flexibility for handling point value data in the IoT DC3 platform.
This commit introduces the redis-exporter service to the docker-compose-grafana-aliyun.yml file, enabling Redis monitoring within the DC3 environment. The service is configured with the necessary logging and network settings to ensure seamless integration.
Added Redis service configuration to both docker-compose-optional.yml and docker-compose-optional-aliyun.yml. This change ensures Redis is available as part of the Docker setup, supporting the application's caching and data storage needs.
The Dockerfile paths in the CI workflow were updated to use the correct service-specific paths instead of the default `./Dockerfile`. This ensures that the correct Dockerfile is used for each service during the build process, avoiding potential errors in multi-service builds.
Removed TDEngine-related files, configurations, and dependencies to streamline the codebase and improve maintainability. This includes deleting TDEngine-specific classes, YAML files, Mapper XML, and removing TDEngine references from the POM files and constant classes. Additionally, updated the Docker CI workflow to ensure consistency.
This commit simplifies the COPY paths in multiple Dockerfiles to use a more consistent and concise format. Additionally, it fixes a typo in the CI workflow and updates the context paths for Docker builds to ensure proper execution.
The commit corrects the variable reference from `steps.version.outputs.varsiables.version` to `steps.varsiables.outputs.version` in the Docker image tagging process. This ensures the correct version is used for tagging images across all services.
Update the JDK setup step to use `actions/setup-java@v4` with the Liberica distribution. Fix the version variable references in docker image tags to correctly use `steps.version.outputs.varsiables.version` instead of `steps.version.outputs.varsiables`.
The build cache configuration (`cache-from` and `cache-to`) has been removed to simplify the Docker build process and reduce dependency on external cache registries. This change aims to streamline the CI workflow and improve build reliability.
Reordered environment variable assignments for better readability and replaced Maven cache step with JDK 21 setup to ensure compatibility with the latest Java version.
Removed the redundant builder stage from all Dockerfiles to streamline the build process. Updated the CI workflow to include Maven build and caching steps, reducing complexity and improving efficiency. These changes aim to enhance maintainability and reduce build times.
Remove local Docker build configurations from docker-compose-aliyun.yml to use pre-built images. Add Spring Actuator and Micrometer Prometheus dependencies to enable application monitoring and metrics collection.
Standardized the use of double quotes in docker-compose files for consistency. Added new docker-compose files for optional and Aliyun configurations to support different deployment environments.
The Docker CI workflows for multiple services (e.g., Gateway, Center Auth, Center Data, etc.) have been removed as they are no longer needed. This cleanup helps reduce repository clutter and maintenance overhead.
Consolidated Dockerfile configurations by removing redundant build steps and updated CI workflows to use consistent naming conventions. This improves maintainability and reduces complexity in the build process.
Updated the version from 2025.2.4 to 2025.2.5 in pom.xml files and various Java classes to reflect the latest release. This change ensures consistency across the codebase and aligns with the new version of the IoT DC3 Platform.
Updated the version from 2025.2.2 to 2025.2.4 in all pom.xml files, Java classes, and CI/CD configurations to reflect the latest release version. This change ensures consistency across the entire project.
The repository configurations for Aliyun, Maven Central, and Sonatype were removed as they are no longer needed. This simplifies the pom.xml file and reduces unnecessary configuration clutter.
Vickey