doc(tutorials): publish the e2e adopter journey tutorial

[stephanbcbauer]

Description

This PR is the final step to merge the feature branch to main and publish the e2e adopter journey tutorial.

• The main parts are the tutorial section itself
• The first tutorial
• The blog entry

note: Please be aware, the links reference to a private fork which currently displays the changes of this PR.

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[arnoweiss]

What's the tractusx-edc version used here? Some payloads look weird like

{
    "querySpec": {
        "offset": 0,
        "limit": 100,
        "filter": "",
        "range": {
            "from": 0,
            "to": 100
        },
        "criterion": ""
    }
}

that looks way different than the openAPI definition.

[stephanbcbauer]

What's the tractusx-edc version used here? Some payloads look weird like

{
    "querySpec": {
        "offset": 0,
        "limit": 100,
        "filter": "",
        "range": {
            "from": 0,
            "to": 100
        },
        "criterion": ""
    }
}

that looks way different than the openAPI definition.

Its 0.5.1 the one which is also mentioned in the related standards

[arnoweiss]

What is filter supposed to mean?
What is criterion supposed to mean?
What is range supposed to mean?

None of these properties for a QuerySpec are mentioned in the openAPI spec for tractusx-edc 0.5.1.

[stephanbcbauer]

What is filter supposed to mean? What is criterion supposed to mean? What is range supposed to mean?

None of these properties for a QuerySpec are mentioned in the openAPI spec for tractusx-edc 0.5.1.

@jkbquabeck , @MoritzDieckmann

[jkbquabeck]

I am not sure who worked on this. Maybe @alexandrudanciu @hemantxpatel or @paullatzelsperger know the answer here.

[hemantxpatel]

Hi, the correct spec will be:

{
    "querySpec": {
        "offset": 0,
        "limit": 100
    }
}

I have referred the existing querySpec from some postman collections. Strangely it doesn't fail or warn, that's why it got skipped.
There are couple of usages in mxd as well. Will raise an issue and fix it.

[arnoweiss]

Hi, the correct spec will be:

{
    "querySpec": {
        "offset": 0,
        "limit": 100
    }
}

I have referred the existing querySpec from some postman collections. Strangely it doesn't fail or warn, that's why it got skipped. There are couple of usages in mxd as well. Will raise an issue and fix it.

@hemantxpatel - Link the ticket here when it's created, please. I've observed the querySpec mechanism behaving strange in a couple of similar situations.

@stephanbcbauer - can you update the relevant parts in the tutorial? Ctl-F "querySpec" should show you all relevant occurences of the error above and I don't have push rights for this repo.

[hemantxpatel]

I raised issue here. eclipse-tractusx/tutorial-resources#166

I've observed the querySpec mechanism behaving strange in a couple of similar situations.

@arnoweiss Since these fields are unknown, they might get silently ignored during Json Serialization and should not affect any functionalities.

[arnoweiss]

Misunderstanding - sorry. I thought you'd open an issue about the EDC's behavior. I'll collect some more examples and then do it myself. Thanks for taking care of this and letting Stephan off my hook.

[stephanbcbauer]

Misunderstanding - sorry. I thought you'd open an issue about the EDC's behavior. I'll collect some more examples and then do it myself. Thanks for taking care of this and letting Stephan off my hook.

To not confuse others, I will adapt the sections before we release the tutorial.