Critical startup failure: Adapter CrashLoopBackOff due to Vault/config.txt access

Dear Cosmin and project representatives,

Thank you very much, Cosmin, for the quick response and for including the project representatives in this thread for visibility and alignment. I appreciate the opportunity to clarify my current situation.

My name is Angel, and I'm a Backend Developer with experience in Java, Spring Boot, and designing REST API applications with layered architecture. Recently, my manager, assigned me the task of deploying and integrating the Simpl-Open project. The initial reason for my assignment was that the team was experiencing compilation issues during an integration attempt, which was thought to be related to my Java profile.

However, as I've delved into the project, I've found that its implementation relies heavily on an ecosystem of tools like Kubernetes, Argo CD, and Vault, all of which are completely outside my current domain of knowledge and experience.

Context of my attempts and current blockers:

Repositories cloned: So far, I have cloned the common, governance-authority, and poc-gaia-edc repositories (the latter contains the adapter).
Steps taken: I've proceeded with the installation of Vault, Kubernetes (via Docker Desktop), and Argo CD, following the installation guide provided in the EU repository.
Current issues:
    The adapter component (from the poc-gaia-edc repo) is stuck in CrashLoopBackOff in Kubernetes. The main error indicates it cannot find the config.txt file it expects to retrieve from Vault.
    I've been working on configuring Vault to allow the adapter to access this config.txt, as the adapter specifically looks for it in a secrets engine named dev-int, whereas my initial Vault setup following the guide used dev.
    The installation documentation I've followed, while helpful, hasn't been 100% comprehensive or clear on all steps or the interconnections between components, which has led to significant difficulties.
Git permission challenges: A point that adds complexity is that I do not have permissions to perform commit or push to the cloned repositories. This prevents me from testing configurations locally or developing/testing simple functionalities (which is one of my manager's goals for me), as Argo CD always deploys the remote Git version. This creates confusion about the workflow and the utility of having the repositories cloned if I cannot interact directly with them for development and testing.

Impact and need for support:

Honestly, I feel quite disoriented and working somewhat "blindly," as I'm heavily reliant on external resources like internet documentation and AI tools. I lack the context and guidance from a senior profile with experience in this domain. It's difficult for me to progress without truly understanding the underlying logic and dependencies between the various components and repositories.

Given your knowledge and experience with Simpl-Open, I would greatly appreciate it if you could:

Point me towards any more detailed or comprehensive documentation/playbooks that cover the full installation and workflow of these interconnected components.
Provide clarification on the dependencies between the different Simpl-Open repositories (e.g., which one depends on which for deployment).
Offer any guidance on the development and testing workflow for a profile without push permissions to the original repository.

I am available for any clarification or to share specific logs and error outputs I'm encountering.

Thank you very much in advance for your time and support.

Best regards,

Ángel