rename terraform-boot project to terra-boot (#472)

baixinsui · web-flow · commit 1dc42ec6b851 · 2025-02-13T05:48:06.000+01:00
diff --git a/docs/architecture.mdx b/docs/architecture.mdx
@@ -29,14 +29,14 @@ It's a spring-boot application that bundles all the modules mentioned above into
 
 The xpanse runtime also needs other systems for it to fully function in a production setup.
 
-| Component      | Description                          |
-| -------------- | ------------------------------------ |
-| Database       | RDBMS based persistence layer        |
-| terraform-boot | Asynchronous Terraform deployer      |
-| tofu-maker     | Asynchronous OpenTofu deployer       |
-| policy-man     | OPA based policy validation engine   |
-| zitadel        | Authentication and authorization     |
-| UI             | ReactJS based user interface         |
-| Redis Cache    | Used for all caching functionalities |
+| Component   | Description                          |
+| ----------- | ------------------------------------ |
+| Database    | RDBMS based persistence layer        |
+| terra-boot  | Asynchronous Terraform deployer      |
+| tofu-maker  | Asynchronous OpenTofu deployer       |
+| policy-man  | OPA based policy validation engine   |
+| zitadel     | Authentication and authorization     |
+| UI          | ReactJS based user interface         |
+| Redis Cache | Used for all caching functionalities |
 
 ![xpanse-stack](../static/img/xpanse-stack-components.excalidraw.png)
diff --git a/docs/developer-setup.mdx b/docs/developer-setup.mdx
@@ -51,15 +51,15 @@ More information about this can be found <Link name='here' url='./spring-profile
 For regular development activities, xpanse needs some predefined applications from its stack based on the use case.
 But in most cases, the dependencies are kept as minimal as possible.
 
-| Component      | Mandatory | Default                             |
-| -------------- | --------- | ----------------------------------- |
-| Database       | No        | H2 Database                         |
-| terraform-boot | No        | terraform-local                     |
-| tofu-maker     | No        | opentofu-local                      |
-| policy-man     | No        | Necessary only for testing policies |
-| zitadel        | No        | We can also use 'noauth' mode       |
-| UI             | No        | We can test APIs directly           |
-| Redis Cache    | No        | Caffeine Cache                      |
+| Component   | Mandatory | Default                             |
+| ----------- | --------- | ----------------------------------- |
+| Database    | No        | H2 Database                         |
+| terra-boot  | No        | terraform-local                     |
+| tofu-maker  | No        | opentofu-local                      |
+| policy-man  | No        | Necessary only for testing policies |
+| zitadel     | No        | We can also use 'noauth' mode       |
+| UI          | No        | We can test APIs directly           |
+| Redis Cache | No        | Caffeine Cache                      |
 
 To set up the above-mentioned components, we can either use a master docker-compose configuration
 which will start all components with default configuration.
@@ -108,7 +108,7 @@ the below steps can be used to install the necessary deployers for local develop
 
 :::info Deployer Development
 These steps are necessary for development activities in the main xpanse application as well as
-deployer applications such as **terraform-boot** or **tofu-maker**.
+deployer applications such as **terra-boot** or **tofu-maker**.
 :::
 
 #### Auto Installation
@@ -118,14 +118,14 @@ If you have an active and stable connection, then there is nothing to be done in
 
 #### Using Docker Images
 
-If you wish to use remote deployers such as **terraform-boot** or **tofu-maker**
+If you wish to use remote deployers such as **terra-boot** or **tofu-maker**
 then you can pull the latest docker containers and configure the xpanse runtime to use it.
 
 In this case, the images already contain the default supported Terraform and OpenTofu versions respectively and
 additionally can install new versions on demand.
 
 ```shell
-docker run -p 9090:9090 -d --name terraform-boot --add-host=host.docker.internal:host-gateway ghcr.io/eclipse-xpanse/terraform-boot:latest
+docker run -p 9090:9090 -d --name terra-boot --add-host=host.docker.internal:host-gateway ghcr.io/eclipse-xpanse/terra-boot:latest
 docker run -p 9092:9092 -d --name tofu-maker --add-host=host.docker.internal:host-gateway ghcr.io/eclipse-xpanse/tofu-maker:latest
 ```
 
diff --git a/docs/observability.mdx b/docs/observability.mdx
@@ -42,7 +42,7 @@ must then be configured in the data producing systems for forwarding the generat
 ### Components Generating Observability Data
 
 - xpanse - activated using spring profile `opentelemetry`
-- terraform-boot - activated using spring profile `opentelemetry`
+- terra-boot - activated using spring profile `opentelemetry`
 - policy-man - activated by starting OpenTelemetry's instrumentation process together with policy-man
 - zitadel - enabled by default
 
diff --git a/docs/service-deployment.mdx b/docs/service-deployment.mdx
@@ -92,7 +92,7 @@ contains all required software pre-installed.
 
 ### Terraform Boot
 
-To offload the service deployment tasks from the xpanse's main runtime engine, we created a project called <Link name={'terraform-boot'} url={'https://github.com/eclipse-xpanse/terraform-boot'}/>.
+To offload the service deployment tasks from the xpanse's main runtime engine, we created a project called <Link name={'terra-boot'} url={'https://github.com/eclipse-xpanse/terra-boot'}/>.
 We used this application for all our Terraform related tasks.
 
 ## OpenTofu
diff --git a/docs/spring-profiles.mdx b/docs/spring-profiles.mdx
@@ -19,7 +19,7 @@ Each profile either enables a certain functionality or provides some default con
 | zitadel-testbed      | Yes                | to use test instance of Zitadel.                                                                                                          |
 | zitadel-local        | Yes                | to use local instance of Zitadel.                                                                                                         |
 | tofu-maker           | No                 | to use remote instance of OpenTofu for deployment.                                                                                        |
-| terraform-boot       | No                 | to use remote instance of Terraform for deployment.                                                                                       |
+| terra-boot           | No                 | to use remote instance of Terraform for deployment.                                                                                       |
 | local-docker-stack   | Yes                | to be used when local docker containers of all xpanse components.                                                                         |
 | dev                  | Yes                | to be used in all local development environments.                                                                                         |
 | opentelemetry        | No                 | to enable OTEL instrumentation and forwarding.                                                                                            |
diff --git a/docs/webhooks.mdx b/docs/webhooks.mdx
@@ -5,7 +5,7 @@ sidebar_position: 11
 # Webhooks
 
 xpanse exposes webhooks for other systems to update the status of tasks.
-Currently, this is used for getting updates from deployment systems such as terraform-boot and tofu-maker.
+Currently, this is used for getting updates from deployment systems such as terra-boot and tofu-maker.
 
 ## Security
 
