Merge pull request #46 from dbeaver/dbeaver/dbeaver-devops#1714-update-devel-to-25-0-0

dbeaver/dbeaver-devops#1714 Updated devel to 25.0.0

Author: ggxed

.env

@@ -1,4 +1,4 @@
-CLOUDBEAVER_VERSION_TAG=24.3.0
+CLOUDBEAVER_VERSION_TAG=25.0.0
 IMAGE_SOURCE=dbeaver
 PODMAN_IMAGE_SOURCE=docker.io/dbeaver
 COMPOSE_PROJECT_NAME=dbeaver

.gitignore

@@ -1,4 +1,5 @@
 .terraform*
 terraform*
 values.yaml
-/.idea
+/.idea
+trusted-cacerts/*

AWS/ecs-fargate/README.md

@@ -33,7 +33,7 @@
    ![alt text](images/image-1.png)
 
    - Ensure that the `alb_certificate_Identifier` variable contains the ID from [AWS Certificate Manager](#importing-an-ssl-certificate-in-aws) corresponding to the domain name specified   in the `CLOUDBEAVER_PUBLIC_URL` variable within variables.tf. The domain name in `CLOUDBEAVER_PUBLIC_URL` must match the domain for which the certificates have been issued.
-   - You can customize the deployment version by updating the `cloudbeaver_version` environment variable. The default version is `24.3.0`.
+   - You can customize the deployment version by updating the `cloudbeaver_version` environment variable. The default version is `25.0.0`.
 
 6. Run `terraform init` and then `terraform apply` in `ecs-fargate` directory to create the ECS cluster and complete the deployment.
 

AWS/ecs-fargate/variables.tf

@@ -25,7 +25,7 @@ variable "cloudbeaver_image_name" {
 variable "cloudbeaver_version" {
   description = "The version of the cluster you want to deploy"
   type = string
-  default = "24.3.0"
+  default = "25.0.0"
 }
 
 variable "alb_certificate_Identifier" {

README.md

@@ -1,6 +1,6 @@
 # CloudBeaver Enterprise deployment
 
-### Version 24.3
+### Version 25.0
 
 CloudBeaver Enterprise is a client-server application.
 It requires server deployment. You can deploy it on a single host (e.g. your local computer) or in a cloud.
@@ -23,6 +23,13 @@ However you can use Docker compose for additional product features such as:
 - [docker-compose](https://docs.docker.com/compose/install/) binary installed and added to your PATH variable. Supported versions 2.10 and above
     - If you install `docker-compose-plugin`, you must use the `docker compose` command instead of `docker-compose`.
 
+### User and permissions changes
+
+Starting from CloudBeaver v25.0 process inside the container now runs as the ‘dbeaver’ user (‘UID=8978’), instead of ‘root’.  
+If a user with ‘UID=8978’ already exists in your environment, permission conflicts may occur.  
+Additionally, the default Docker volumes directory’s ownership has changed.  
+Previously, the volumes were owned by the ‘root’ user, but now they are owned by the ‘dbeaver’ user (‘UID=8978’).  
+
 ### Configuring and starting the CloudBeaver cluster
 1. Clone repository
    ```sh
@@ -68,5 +75,6 @@ or replace `docker-compose.yml` with `podman-compose.yml` and use `podman-compos
 3. Restart the cluster: `docker-compose up -d` or `docker compose up -d`
 
 ### Older versions:
+- [24.3.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/24.3.0)
 - [24.2.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/24.2.0)
 - [24.1.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/24.1.0)

cloudbeaver-db-init.sql

@@ -6,6 +6,7 @@ volumes:
   postgres_data: {}
   nginx_ssl_data: {}
   nginx_conf_data: {}
+  trusted_cacerts: {}
 
 services:
   nginx:
@@ -30,6 +31,7 @@ services:
     volumes:
       - cloudbeaver:/opt/cloudbeaver/workspace
       - cloudbeaver_certs:/opt/cloudbeaver/conf/certificates/
+      - trusted_cacerts:/opt/cloudbeaver/workspace/.data/custom/
     environment:
       - CLOUDBEAVER_DB_DRIVER=${CLOUDBEAVER_DB_DRIVER}
       - CLOUDBEAVER_DB_URL=${CLOUDBEAVER_DB_URL}

docker-compose-host.yml

@@ -6,6 +6,7 @@ volumes:
   postgres_data: {}
   nginx_ssl_data: {}
   nginx_conf_data: {}
+  trusted_cacerts: {}
 
 networks:
   cloudbeaver-private-net:
@@ -36,6 +37,7 @@ services:
     volumes:
       - cloudbeaver:/opt/cloudbeaver/workspace
       - cloudbeaver_certs:/opt/cloudbeaver/conf/certificates/
+      - trusted_cacerts:/opt/cloudbeaver/workspace/.data/custom/
     environment:
       - CLOUDBEAVER_DB_DRIVER=${CLOUDBEAVER_DB_DRIVER}
       - CLOUDBEAVER_DB_URL=${CLOUDBEAVER_DB_URL}
@@ -60,7 +62,6 @@ services:
     image: ${IMAGE_SOURCE:-dbeaver}/cloudbeaver-postgres:16
     volumes:
       - postgres_data:/var/lib/postgresql/data
-      - ./cloudbeaver-db-init.sql:/docker-entrypoint-initdb.d/cb-init.sql
     environment:
       - POSTGRES_DB=cloudbeaver
       - POSTGRES_USER=${CLOUDBEAVER_DB_USER}

docker-compose.yml

@@ -3,4 +3,4 @@ name: cb
 description: A Helm chart for CloudBeaver application
 type: application
 version: 0.0.1
-appVersion: 24.3.0
+appVersion: 25.0.0

k8s/Chart.yaml

@@ -10,6 +10,13 @@
 
 [//]: # (* [Nginx load balancer](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-helm/) and [Kubernetes Helm plugin](https://helm.sh/docs/topics/plugins/) added to your `k8s`)
 
+### User and permissions changes
+
+Starting from CloudBeaver v25.0 process inside the container now runs as the ‘dbeaver’ user (‘UID=8978’), instead of ‘root’.  
+If a user with ‘UID=8978’ already exists in your environment, permission conflicts may occur.  
+Additionally, the default Docker volumes directory’s ownership has changed.  
+Previously, the volumes were owned by the ‘root’ user, but now they are owned by the ‘dbeaver’ user (‘UID=8978’).  
+
 ### How to run services
 - Clone this repo from GitHub: `git clone https://github.com/dbeaver/cloudbeaver-deploy`
 - `cd cloudbeaver-deploy/k8s`