From 269865244204ff9d353b69d5a56bd5f8e5fb0257 Mon Sep 17 00:00:00 2001 From: "Florian Rusch (ZF Friedrichshafen AG)" Date: Fri, 1 Dec 2023 06:59:43 +0100 Subject: [PATCH 1/2] fix: replace KeyCloak with Keycloak --- blog/2023-11-22-release_tutorials.mdx | 8 +-- .../operation-view/deployment.md | 72 +++++++++---------- .../tractusx-connector-azure-vault/README.md | 14 ++-- .../tractusx-connector-memory/README.md | 14 ++-- .../charts/tractusx-connector/README.md | 14 ++-- .../docs/migration/Version_0.4.x_0.5.x.md | 26 +++---- .../docs/samples/example-dataspace/README.md | 12 ++-- docs/tutorials/e2e.md | 2 +- docs/tutorials/e2e/inform/architecture.md | 2 +- static/img/architecture.drawio | 2 +- static/img/architecture.drawio.svg | 6 +- static/img/irs_buidling_block_decentral.svg | 6 +- 12 files changed, 89 insertions(+), 89 deletions(-) diff --git a/blog/2023-11-22-release_tutorials.mdx b/blog/2023-11-22-release_tutorials.mdx index 3a0e4dc9518..fb5fc7cb23b 100644 --- a/blog/2023-11-22-release_tutorials.mdx +++ b/blog/2023-11-22-release_tutorials.mdx @@ -24,8 +24,8 @@ This new section aims to provide structured and detailed educational content for ## Details of the First E2E Adopter Journey Tutorial -This tutorial is built for employees of the IT department who operates the IT stack of an adopter (data provider/consumer). It shows how to operate the various Tractus-X components in combination with each other. -It also explains the basic connection with the core services (e.g. KeyCloak and MIW), as provided by an operating company. +This tutorial is built for employees of the IT department who operates the IT stack of an adopter (data provider/consumer). It shows how to operate the various Tractus-X components in combination with each other. +It also explains the basic connection with the core services (e.g. Keycloak and MIW), as provided by an operating company. ![Five steps to gain value](@site/static/img/five_steps_to_gain_value.drawio.svg) @@ -48,7 +48,7 @@ Please dont forget to add the label `documentation` to your discussion. ::: -### Accessing the Tutorial +### Accessing the Tutorial The E2E Adopter Journey Tutorial is now available and can be accessed through the [Tractus-X tutorial section](https://eclipse-tractusx.github.io/docs/tutorials). We invite our community members to engage with this new resource and enhance their understanding of the Tractus-X ecosystem. @@ -61,6 +61,6 @@ For further information and to access the tutorial, please visit the [Tractus-X ## Stay Connected Follow our [news section](https://eclipse-tractusx.github.io/blog) and join our [Tractus-X mailing list](https://eclipse-tractusx.github.io/docs/oss/how-to-contribute/#dev-mailinglist) -and be part of our [Matrix Chat from Eclipse Tractus-X](https://chat.eclipse.org/#/room/#tools.tractus-x:matrix.eclipse.org) +and be part of our [Matrix Chat from Eclipse Tractus-X](https://chat.eclipse.org/#/room/#tools.tractus-x:matrix.eclipse.org) For more details about Tractus-X, visit the official [Eclipse Tractus-X Project Page](https://projects.eclipse.org/projects/automotive.tractusx). diff --git a/docs-kits/kits/knowledge-agents/operation-view/deployment.md b/docs-kits/kits/knowledge-agents/operation-view/deployment.md index a0ddf80ffe8..1686dc9c906 100644 --- a/docs-kits/kits/knowledge-agents/operation-view/deployment.md +++ b/docs-kits/kits/knowledge-agents/operation-view/deployment.md @@ -4,7 +4,7 @@ title: Deployment --- «Tier/OEM-Environment»Tier/OEM«System»IRS«System»EDC Consumer«System»IAM/KeyCloak«System»IAM/Keycloak«System»MIW«System»EDC_Provider_OEM«System»EDC_Provider_Tier1 \ No newline at end of file +--> From 7b7db15fbdcddcd0b79511e5c3a02e2777b3d46f Mon Sep 17 00:00:00 2001 From: "Florian Rusch (ZF Friedrichshafen AG)" Date: Tue, 2 Jan 2024 10:08:21 +0100 Subject: [PATCH 2/2] Fix [kK]ey[cC]loack as well --- .../kits/Data Chain Kit/page_software-operation-view.md | 6 +++--- .../Data Chain Kit/Success Stories/page_trace-x_story.mdx | 6 +++--- .../Data Chain Kit/Success Stories/page_trace-x_story.mdx | 6 +++--- .../Data Chain Kit/Success Stories/page_trace-x_story.mdx | 6 +++--- 4 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs-kits/kits/Data Chain Kit/page_software-operation-view.md b/docs-kits/kits/Data Chain Kit/page_software-operation-view.md index 8b5dfec06ab..0a2a23199f7 100644 --- a/docs-kits/kits/Data Chain Kit/page_software-operation-view.md +++ b/docs-kits/kits/Data Chain Kit/page_software-operation-view.md @@ -37,11 +37,11 @@ This local deployment is an easy installation with helm. This setup is built to 1. [Docker](https://docs.docker.com/get-docker/) is installed and the Docker deamon is running with at least 8GB of memory 2. [helm](https://helm.sh/docs/intro/install/) is installed -3. [Minikube](https://minikube.sigs.k8s.io/docs/start/) is installed and running. +3. [Minikube](https://minikube.sigs.k8s.io/docs/start/) is installed and running. You can also use any other local Kubernetes cluster, this guide is just using Minikube as a reference. ```bash - minikube start --memory 8192 --cpus 2 + minikube start --memory 8192 --cpus 2 ``` _Optional_: enable minikube metrics @@ -112,7 +112,7 @@ error: timed out waiting for the condition on deployments/irs-frontend The minikube dashboard will give you feedback on how the status of the deployment currently is: ```bash - minikube dashboard + minikube dashboard ``` Make sure you select the namespace **irs**: diff --git a/docs-kits_versioned_docs/version-23.09/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx b/docs-kits_versioned_docs/version-23.09/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx index a3da45fc0ae..7e07727a49e 100644 --- a/docs-kits_versioned_docs/version-23.09/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx +++ b/docs-kits_versioned_docs/version-23.09/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx @@ -25,11 +25,11 @@ All this saves' costs by seamlessly tracking parts as well as creates trust thro ![success2](@site/static/img/IRS2.png) -Applying and using the Item Relationship Service had the following benefits: +Applying and using the Item Relationship Service had the following benefits: -* With the decision using the IRS we could speed our development of Trace-X through out the scope of their helm charts including a running service with test data. That alone was very benefitial to have a stable environment with data +* With the decision using the IRS we could speed our development of Trace-X through out the scope of their helm charts including a running service with test data. That alone was very beneficial to have a stable environment with data * The IRS fulfills a high level of quality in code which provides a reliable service -* The deployment via helm charts has been built so that it can fit in existing architecture components through out configuration like the Digital Twin Registry, the EDC, Semantic Hub, Keycloack and others. This enabled Trace-X to configure the Service smoothly into the architecture of the application +* The deployment via helm charts has been built so that it can fit in existing architecture components through out configuration like the Digital Twin Registry, the EDC, Semantic Hub, Keycloak and others. This enabled Trace-X to configure the Service smoothly into the architecture of the application * The IRS abstracts the communication with partners along the supply chain, that makes it easy to build business processes on that. It abstracts a technical level to a logical level to enhance the speed of implementation of a Software Provider * The IRS with the standardized API provides a data interoperability level on data chains * The Team behind the IRS is fast in implementing and adapting new features diff --git a/docs-kits_versioned_docs/version-23.12/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx b/docs-kits_versioned_docs/version-23.12/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx index a3da45fc0ae..7e07727a49e 100644 --- a/docs-kits_versioned_docs/version-23.12/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx +++ b/docs-kits_versioned_docs/version-23.12/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx @@ -25,11 +25,11 @@ All this saves' costs by seamlessly tracking parts as well as creates trust thro ![success2](@site/static/img/IRS2.png) -Applying and using the Item Relationship Service had the following benefits: +Applying and using the Item Relationship Service had the following benefits: -* With the decision using the IRS we could speed our development of Trace-X through out the scope of their helm charts including a running service with test data. That alone was very benefitial to have a stable environment with data +* With the decision using the IRS we could speed our development of Trace-X through out the scope of their helm charts including a running service with test data. That alone was very beneficial to have a stable environment with data * The IRS fulfills a high level of quality in code which provides a reliable service -* The deployment via helm charts has been built so that it can fit in existing architecture components through out configuration like the Digital Twin Registry, the EDC, Semantic Hub, Keycloack and others. This enabled Trace-X to configure the Service smoothly into the architecture of the application +* The deployment via helm charts has been built so that it can fit in existing architecture components through out configuration like the Digital Twin Registry, the EDC, Semantic Hub, Keycloak and others. This enabled Trace-X to configure the Service smoothly into the architecture of the application * The IRS abstracts the communication with partners along the supply chain, that makes it easy to build business processes on that. It abstracts a technical level to a logical level to enhance the speed of implementation of a Software Provider * The IRS with the standardized API provides a data interoperability level on data chains * The Team behind the IRS is fast in implementing and adapting new features diff --git a/docs-kits_versioned_docs/version-3.1.0/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx b/docs-kits_versioned_docs/version-3.1.0/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx index a3da45fc0ae..7e07727a49e 100644 --- a/docs-kits_versioned_docs/version-3.1.0/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx +++ b/docs-kits_versioned_docs/version-3.1.0/kits/Data Chain Kit/Success Stories/page_trace-x_story.mdx @@ -25,11 +25,11 @@ All this saves' costs by seamlessly tracking parts as well as creates trust thro ![success2](@site/static/img/IRS2.png) -Applying and using the Item Relationship Service had the following benefits: +Applying and using the Item Relationship Service had the following benefits: -* With the decision using the IRS we could speed our development of Trace-X through out the scope of their helm charts including a running service with test data. That alone was very benefitial to have a stable environment with data +* With the decision using the IRS we could speed our development of Trace-X through out the scope of their helm charts including a running service with test data. That alone was very beneficial to have a stable environment with data * The IRS fulfills a high level of quality in code which provides a reliable service -* The deployment via helm charts has been built so that it can fit in existing architecture components through out configuration like the Digital Twin Registry, the EDC, Semantic Hub, Keycloack and others. This enabled Trace-X to configure the Service smoothly into the architecture of the application +* The deployment via helm charts has been built so that it can fit in existing architecture components through out configuration like the Digital Twin Registry, the EDC, Semantic Hub, Keycloak and others. This enabled Trace-X to configure the Service smoothly into the architecture of the application * The IRS abstracts the communication with partners along the supply chain, that makes it easy to build business processes on that. It abstracts a technical level to a logical level to enhance the speed of implementation of a Software Provider * The IRS with the standardized API provides a data interoperability level on data chains * The Team behind the IRS is fast in implementing and adapting new features