Docusaurus kits

[bcronin90]

Add documentation kit for use in Docusaurus.

There is one pain point right now: Significant parts of the docusaurus documentation are similar or identical to existing documentation. If anyone has a smart idea how to de-duplicate this, please tell me.

_{Brendan Cronin brendan.cronin@mercedes-benz.com, Mercedes-Benz Tech Innovation GmbH, legal info/Impressum}

[bcronin90]

@stephanbcbauer This needs to be added

[stephanbcbauer]

@bcronin90 i had a discussion with Daniel Miehle. This is something which should be on another layer. So not in the connectorKit. This file can be deleted

[bcronin90]

I think it'd be sensible to at least link to this information. If I wanted to set up an EDC right now, I frankly wouldn't know where to get a BPN.

[bcronin90]

In the context of EDC, I would call the contract agreement and its policies an authorization. Though the enforcement of these is kind of intransparent. Maybe the others can comment on this?

[jimmarino]

In EDC there is access policy (not advertised) and usage policy (advertised), which is codified by a ContractDefinition. The union of those determines if a client can acquire an asset. HTH.

[DominikPinsel]

Great PR :) Will merge after the open comments are resolved!

[DominikPinsel]

Maybe we can document how these files are generated. There is a release documentation started at /docs/release. The idea is to have

• a checklist of things to do, before releasing a software
• a how to release the software

So this should be the right place

[stephanbcbauer]

@DominikPinsel yes and no :) the problem here…. the files are not generated within our repository. They are created via docusaurus plug-ins.?

https://www.npmjs.com/package/docusaurus-plugin-openapi-docs

[bcronin90]

I'll document it based on that.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[bcronin90]

Now that this repo has been declared dead effective immediately, what should happen to PRs like this? @stefan-ettl

[ndr-brt]

Now that this repo has been declared dead effective immediately, what should happen to PRs like this? @stefan-ettl

You can re-create the PR on https://github.com/catenax-ng/tx-tractusx-edc
I went with git format-patch and git apply and it was pretty smooth

[bcronin90]

Now that this repo has been declared dead effective immediately, what should happen to PRs like this? @stefan-ettl

You can re-create the PR on https://github.com/catenax-ng/tx-tractusx-edc I went with git format-patch and git apply and it was pretty smooth

Should I be able to push a branch to tractusx-edc? Because I get a 403. Or do I need to rebase a branch from here onto their main and then PR from that?

[ndr-brt]

Now that this repo has been declared dead effective immediately, what should happen to PRs like this? @stefan-ettl

You can re-create the PR on https://github.com/catenax-ng/tx-tractusx-edc I went with git format-patch and git apply and it was pretty smooth

Should I be able to push a branch to tractusx-edc? Because I get a 403. Or do I need to rebase a branch from here onto their main and then PR from that?

the 403 is an unauthorized error so it's not related to the "different history", but yeah, it should be pretty easy to do adding the tx-tractusx-edc as a remote (or adding product-edc to tx-tractusx-edc as a remote) then soft resetting the branch on another branch based on tractusx history.

[florianrusch-zf]

I closed this PR, because we already moved to https://github.com/eclipse-tractusx/tractusx-edc/