fix: updated reference links to the Supporting Infrastructure Deployment

[MarkAshraf96]

The reference links to the TXDC Supporting Infrastructure were outdated and routes to files that no longer exits.

Closes #399

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[paullatzelsperger]

First of all, thanks for you contribution! The document you worked on refers to the "business test" environment, which doesn't exist anymore, so the Local TXDC Setup document should be deleted.
However, if you like, instead of deleting the document, you could document and explain how the deployment tests (cf .github/workflows/deployment-test.yaml) work, and how to run them locally?

Please also be aware of PR #354

[MarkAshraf96]

So which document should I follow if I wanna setup the Tractus-x EDC on my machine and run a basic scenario?
I would also like to know how the documentation of the test could be a replacement for the documentation of the setup, as I would like to do that contribution.

[paullatzelsperger]

So which document should I follow if I wanna setup the Tractus-x EDC on my machine and run a basic scenario?

That's the point - there isn't one at the moment. And to be clear, the "Local TXDC..." document doesn't show you that either, it only shows you how to run a bunch of tests, which have been replaced by more appropriate and efficient tests.

I think there are two general issues here:

1. showing (and documenting) how one TX-EDC connector can be operated, what the required configuration is, etc. For that, I would suggest looking at the deployment-test.yaml file, because all that's needed is already there.
2. showing (and documenting) a scenario, where two connectors run in a dataspace, what the configuration for each one is, how they communicate, what requests can be executed against either one, etc. That would effectively be a "demo dataspace" and it is certainly the more labor-intense of the two, by a wide margin. For that, you could look at AbstractCatalogTest.java and AbstractHttpConsumerPullWithProxyTest.java

I would also like to know how the documentation of the test could be a replacement for the documentation of the setup, as I would like to do that contribution.

That is admirable, i would suggest you start with issue 1. document how people can run one connector. When you do that, also take note of PR #370 which converts all helm charts to be self-contained. Once that is accepted into the code base, you could venture on to implement/document point 2. the "mini dataspace".

[stephanbcbauer]

#314 should be the step by step guide? @MarkAshraf96

[paullatzelsperger]

@MarkAshraf96 @stephanbcbauer I will close this PR, because the "supporting infrastructure" does not exist anymore (e.g. DAPS is scheduled to be removed in 0.5.0) and we now have an "example dataspace" in docs/samples that shows how to run two connectors.

If you disagree, I'd be keen to hear your reasoning, but we could re-open this PR.